Job Description

Position: Microsoft Dynamics 365

Duration: Depends on Project

Location: Minnesota (Remote)

Provide project resources that are Microsoft Certified in these areas: Dynamics 365 Fundamentals, Dynamics 365 Sales Functional Consultant, and/or Dynamics 365 Customer Service Functional Consultant.

Project Schedule

• Anticipated Project Start Date: As soon as a work order can be executed
• Anticipated End Date: Per contracted vendor's proposed timeline, if and as approved by the State

Resource Need

• This request is for a vendor to provide services on a deliverables basis, utilizing however many resource(s) are necessary to complete the work.

Resource(s) Minimum Qualification

• 2 years of experience with Microsoft Dynamics 365 as relates to the resource's role in the project.

Vendor (Company) Desired Qualifications

• Experience performing discovery, requirements gathering, and/or planning for Microsoft Dynamics 365 implementations.
• Experience implementing Microsoft Dynamics 365 that included customization.
• Experience using organizational change management to fully develop the maximum utilization of MS D365 and leverage the Microsoft platform.
• Experience working with large government entities.
• Experience with Agile methodologies for CRM implementation.
• Ability to provide project resources that are Microsoft Certified in these areas: Dynamics 365 Fundamentals, Dynamics 365 Sales Functional Consultant, and/or Dynamics 365 Customer Service Functional Consultant

Description of Project

The Minnesota Department of Information Technology Services (MNIT), partnering with the Minnesota Department of Health (MDH), is seeking a vendor to perform services pertaining to the implementation of Microsoft Dynamics 365 (MS D365) for the MDH Pharmaceutical Economics Policy and Research (PEPR) program.

The PEPR program is part of the Health Economics Program (HEP) in the Health Policy Division at MDH. Pursuant to statutory requirements, PEPR has been collecting data on prescription drug prices from drug manufacturers and other health care entities since 2022. Due to new legislation, PEPR additionally began collecting data from drug wholesalers, Pharmacy Benefit Managers (PBMs), pharmacies, and other providers in 2024. PEPR has experienced a significant increase in email activity, contact management needs, and other program operational needs due to the expanded portfolio.

PEPR wishes to implement Microsoft Dynamics 365 to support its work related to communicating with reporting entities and the public. The State of Minnesota uses Microsoft products for most day-to-day business functions, including Outlook and Teams. PEPR has a shared mailbox for communicating with the public. Microsoft Dynamics 365 will be utilized for management of the shared mailbox and associated compliance functions.

PEPR has a fully developed web portal built in Azure where reporting entities and any associated third-party administrators register and submit the drug pricing reports. This web portal ties to the PEPR database and research environments. Microsoft Dynamics 365 will not replace this reporting environment. The only integration with the existing PEPR data system will be a one-way flow from the Azure database/portal to Microsoft Dynamics 365 of 1) the relationships established in the portal, and 2) the status of reports in the portal.

The initial work under this engagement will be the Discovery and Specifications phases of the project.

Initial Project Tasks/Deliverables:

The vendor will build upon and refine the requirements identified by the State thus far for the implementation of Microsoft Dynamics 365 for PEPR. See the Buyer Attachment PEPR CRM Requirements for the requirements currently identified. See also the Buyer Attachment PEPR Team Composition and Schedules for additional details on the number of individuals that the vendor will need to engage with and their general schedules.

Specific vendor tasks/deliverables are as follows:

Phase 1 - Discovery

• Gain familiarity with the business team.
• Review relevant current documentation.
• Continue requirements mapping.
• Review standard processes to identify gaps.
• Identify required workflows.
• Capture required fields and business rules.
• Gather integration requirements in conjunction with MNIT technical team.
• Provide project communication/documentation on an ongoing basis via SharePoint, weekly/biweekly project status meetings, and monthly project sponsor meetings.

Phase 2 - Specifications

• Prepare detailed specifications document for each functional area.
• Prepare user stories.
• Prepare wireframes.
• Prepare detailed acceptance criteria.
• Prepare field mapping.
• Review records earmarked for migration.
• Prepare migration plan.
• Prepare overall project plan for implementation.
• Provide proposed implementation timeframe/schedule.
• Provide proposed implementation cost.
• Provide project communication/documentation on an ongoing basis via SharePoint, weekly/biweekly project status meetings, and monthly project sponsor meetings.

Job Tags

Similar Jobs