OhioMHAS - IT Modernization

In an MBE set-aside solicitation, only those bidders/suppliers with an active MBE certification at the time the solicitation closes can submit a response

SRC0000026097

1/15/2025 2:00:00 PM

Round 2, has been issued to update the following:
Inquiry End Date 12/30/2024 01/15/2025.
Closing Date 01/02/2025 01/17/2025.
I. PURPOSE

The Ohio Department of Mental Health and Addiction Services (OhioMHAS) is seeking proposals from qualified contractors to modernize our existing .NET-based application, SQL server database, and reporting systems to leverage the latest dot net technology and standards, Microsoft Azure environment and follow best practices to improve system performance, scalability. Migrating to the latest version of .NET will ensure that the application remains secure, supported, and takes advantage of the latest features and enhancements offered by the platform.

II.  BACKGROUND

Ohio MHAS developed dot net applications with SQL server backend, hosted in on-prem. The primary objectives of the modernization project are:

.Net Application: Upgrade the .NET framework, enhance the user interface/experience, refactor code for performance improvements, and introduce modern security protocols, host in cloud.

SQL server: Migrate to a newer version, optimize database performance, and implement data security best practices.

Reporting System: Implement Report integration module so applications use tableau  reports instead of cognos reports.

III.  SCOPE OF WORK AND DELIVERABLES

Below is the scope of work divided into sections:

Section 1: Upgrade Projects to .Net framework 4.8.1

Section 2: Upgrade the project to latest .Net version 8

Section 3: Move from TFS to Azure DevOps
All the applications are maintained in the Application Portfolio spreadsheet. Migrate the application, database and required user stories to Azure DevOps. Decommission the TFS server.

Section 4: Legacy servers decommission

1. Redeploy the following apps from old Legacy server to Azure App service.
   1. Phone Directory
   2. Old LACTS
2. Archive the app deployment files into Azure Devops and retain for 1 year before deleting.
3. Decommission Legacy servers.

Section 5: Migrate services to Azure API Management
Host the following services as appservice and manage it in API service Management.

Consume these services from all the other applications.

Section 6: Migrate console apps to Logic Apps
Approximately 10 console apps. Migrate to Azure Logic apps & Azure Function following best practices like logging, Email failure notification, Infrastructure as a code (use ARM templates), Azure Governance document.

Create sub logic apps for code reusability. Logic apps should be deployed in 4 environments (Dev, QA, UAT, Preprod and Prod).

These jobs will still connect to On-prem database. Once the console apps are deployed to Azure, release the MHservers and CSS servers for console applications. There is total 7 servers.

Section 7: OPS Console Apps
There are approximately 25 console apps. Refactor the console apps, upgrade to latest framework and consolidate. Host them in Azure as Logic apps or Azure function.

Section 8: Migrate Application Reports to use Tableau/SSRS
POC already created and placed in the shared folder for App Integration with Tableau. Create standard library in .Net standard and consume it in the following Applications:

Section 9: Upgrade and Re-host OCMH in Azure Environment

Section 10: SSIS Packages Upgrade
Migrate SSIS old version to latest version 2019. There are around 40 SSIS packages.

Section 11: DB Cross Reference
Analyze and evaluate all the DB cross reference. Design APIS and host in theAzure API Management Service.

Selected vendor will work closely with the App dev Team to implement the above sections. While working in each of the sections, Vendor should implement best practices, follow security standards.
All the .Net upgrade projects in all the above sections should address the following.

1. Move code from TFS to Azure Dev Ops
2. Migrate from .Net 4.5 to .Net 4.8.1
3. Migrate from .Net core/.Net 6 to .Net 8
4. Update Nuget packages to latest version.
5. Jquery libraries compatibility
6. Upgrade Third Party Libraries to latest version.
7. Remove any unused nuget packages, third party libraries.
8. Checkmarx security risks
9. Add Logging in all the application.
10. Add Header, Footer, Logo ,Styles from Innovate Ohio
11. Build Pipeline for deployment.

Create common branding code to be used across all the .Net application utilizing Free
user experience digital toolkit | InnovateOhio

Deliverable & Payment Structure

The following deliverables have been identified as critical milestones for the successful completion of the project. Payment for each deliverable will be made in part upon acceptance of each milestone. The final acceptance of all deliverables will trigger the
final payment.

IV.   MINIMUM QUALIFICATIONS OF CONTRACTOR

Proposals should include the following:

1. Detailed plan for development, Testing, Deployment, including timelines, resource requirements, and milestones.
2. Company background, relevant experience, and references.
3. Staff details including skillset and experience.
4. Detailed cost breakdown, including implementation, maintenance, and support fees.
5. Provide case studies or references of clients in similar sectors.
6. Support and Knowledge Transition plan to the App Dev/DBA team.

The minimum qualifications of the project staff shall be: Contractor shall not be subject to an “unresolved” finding for recovery under Section 9.24 of Ohio Revised Code.

PART FOUR: EVALUATION OF PROPOSALS

I. EVALUATION PROCESS

OhioMHAS’s evaluation process of responses submitted to this request may consist of up to four distinct phases:

1. OhioMHAS’s initial review of all proposals for timely submission;
2. An evaluation committee review of the proposals for defects and scoring;
3. OhioMHAS’s request for more information (clarifications, interviews, presentations, and/or demonstrations); and,
4. Negotiations or best offer requests.

At its sole discretion, OhioMHAS will determine whether phases three and/or four are necessary under this RFP, reserving for itself the ability to eliminate or add phases three or four at any time during the evaluation process. OhioMHAS may add or remove subphases to phases 2 through 4 at any time if MHAS believes doing so will improve the evaluation process.

II. PROPOSAL EVALUATION CRITERIA

In the proposal evaluation phase, OhioMHAS staff or reviewers selected by OhioMHAS (the committee) will rate the proposals submitted in response to this RFP based on the following criteria and weight assigned to each criterion.

P006364 DMH Rhodes Tower Floor 33 Information Technology Division Columbus