Award Recommendation and Evaluation Synopsis - 250000002570 - MDSS Phase 2 - NIA1 - 260000000829.pdf

Michigan.gov/MiProcurement

Version 2024-2 Page 1 of 108

AWARD RECOMMENDATION

Notice of Intent to Award Number: 260000000829

Notice of Intent to Award Date: 9/3/2026

The Department of Technology, Management, & Budget’s Procurement office has completed the evaluation of Request for Proposal (RFP) - 250000002570 - MDHHS - Michigan Disease Surveillance System (MDSS) - Phase 2 and has recommended an award to CDW Government LLC. in the amount of $10,236,028.00, pending State Administrative Board approval, if applicable. More information on the State Administrative Board can be found at: State Administrative Board.

Bidders who were not recommended for the award are encouraged to schedule a debriefing session with the Solicitation Manager. The debriefing session will provide the bidder with the State’s rationale on why the bidder was not recommended for the award.

The Solicitation Manager may be contacted as follows:

Mecca Martin, Solicitation Manager

Email: MartinM42@michigan.gov

Phone: 517-230-5694

Public copies of all bidder proposals can be found here: DTMB - Bid Proposals (michigan.gov)

Background Information:

This Request for Proposal (RFP) was to solicit responses for selection of a Contractor to provide Michigan Disease Surveillance System Phase 2. The term of this contract is 5 years, with up to 5 renewal options.

Bidders:

The RFP was posted on SIGMA VSS on June 10th, 2025, for 7 weeks. The following bidders submitted proposals by the published due date of July 31st, 2025.

Bidder Address, City, State, Zip Code SDVOB* GDBE**

Acro Service Corporation 39209, W. Six Mile Road, Suite 160, Livonia, MI 48152 No No

AHEAD, Inc. 444 W Lake Street 30th Floor Chicago IL 60606 No No

CDW Government LLC 230 N. Milwaukee Avenue, Vernon Hills, IL 60061 No No

Conduent Public Health Solutions, Inc.

100 Campus Drive, Suite 200, Florham Park, NJ 07932 No No

Deloitte Consulting LLP 30 Rockefeller Plaza New York, NY 10112 No No

Effectual Inc. 163 Waterfront Street, Suite 450 Oxon Hill, MD 20745 No No

People.Health 1734 Crooks Road Troy, MI 48084 No No https://www.michigan.gov/dtmb/policies/state-ad-board mailto:MartinM42@michigan.gov https://www.michigan.gov/dtmb/procurement/contractconnect/bid-proposals https://www.michigan.gov/dtmb/procurement/contractconnect/bid-proposals

Version 2024-2 Page 2 of 108

Bidder Address, City, State, Zip Code SDVOB* GDBE**

Pronix Inc. 666 Plainsboro Rd, Suite# 1361, Plainsboro, NJ 08536, No No

RADCube LLC 1119 Keystone Way N, Carmel, IN 46032 No No

RICEFW Technologies 2150 Association Dr Ste 270 Okemos MI 48864-

No No

Strategic Solutions Group 300 First Avenue, Suite 103 Needham, MA 02494 No No

The Hathaway Group 3079 Halfway Road The Plains, VA 20198 No No

VivSoft Technologies 13221 Woodland Park Rd Suite 310, Herndon, VA 20171 No No

*SDVOB: Service-Disabled Veteran Owned Business **GDBE: Geographically Disadvantaged Business Enterprise

Version 2024-2 Page 3 of 108

EVALUATION SYNOPSIS

I. Evaluation Process

A Responsible Vendor is a vendor that demonstrates it has the ability to successfully perform the duties identified by the solicitation. A Responsive proposal is one that is submitted in accordance with the solicitation instructions and meets all mandatory requirements identified in the solicitation.

The State evaluated each proposal based on the following factors:

Technical Criteria Name Weight

1. Schedule A – Statement of Work 40

2. Schedule A – Table 1 - Business Specification Worksheet 30

3. Vendor Questions Worksheet 15

4. Resume Templates 15

Total 100

The full evaluation process is stated in the RFP Proposal Instructions.

II. Evaluation Method

Responses to this solicitation were reviewed by Solicitation Manager in collaboration with Subject Matter Experts; Joint Evaluation Committee, which consisted of the following individuals:

Voting Advisory

Abigail Cheney – Department of Health and Human Services

David Barks - Department of Technology Management & Budget

Danielle Lefere – Department of Health and Human Services

Derick Chia - Department of Health and Human Services

Mecca Martin – Solicitation Manager Department of Technology Management & Budget

Jonathan Dashner – Department of Technology Management and Budget

Sandhya Muppa - Department of Technology Management & Budget

Jessica Davey - Department of Health and Human Services

Glen Dudasik - Department of Health and Human Services

Seth Eckel - Department of Health and Human Services

Version 2024-2 Page 4 of 108

Voting Advisory

Farhiya Hajabdi - Department of Health and

Ed Hartwick - Department of Health and Human

Craig Henry - Department of Health and Human Services

Shannon Johnson - Department of Health and Human Services

Prabhakar Koduri - Department of Technology Management & Budget

Jeremy Kuo - Department of Health and Human Services

Corbin Montry - Department of Technology Management & Budget

Vinod Narmat - Department of Technology Management & Budget

Hemalatha Nallamothu - Department of Technology Management & Budget

Brad Olsen - Department of Health and Human Services

Kamalakar Pinnapureddy - Department of Technology Management & Budget

Gurumurthy Ramachandran - Department of Technology Management & Budget

Talisha Rice - Department of Health and Human Services

Ashley Sharp - Department of Health and Human Services

Ramakrishna Vakka - Department of Technology Management & Budget

Catherine Washington - Department of Health and Human Services

James Waweru - Department of Health and Human

Version 2024-2 Page 5 of 108

Voting Advisory

Molly Welch Marahar - Department of Health and

Version 2024-2 Page 6 of 108

Evaluation Results

Evaluation Criteria:

A. Bidder # 1

The Evaluation Team determined that Acro Service Corporation, based on a score of 83.6922, did meet the requirements of this RFP. This determination was accomplished by evaluating their responses to the Technical Evaluation Criteria.

1. Schedule A – Statement of Work The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies were noted:

Schedule A - Statement of Work

Requirement Comment Deduction

15. Transition Responsibilities Bidder Box 1

Bidder must provide a detailed transition-out plan in Schedule F – Transition Out Plan, including any roles or responsibilities expected of the State.

The plan must demonstrate the steps to migrate between Bidder’s Solution and third-party Solutions. (Transition is defined per Terms and Conditions Section 16.3).

Not enough detail in the transition out plan.

0.25

16. Documentation Bidder Box 1

Bidder must provide details on, and examples of, documentation to meet the requirements set forth in this section.

Did not provide examples. 0.25

24. Project Management Bidder Box 3

Bidders must provide a milestone schedule and associated deliverables below.

Bidder didn’t use the table but did provide the answer elsewhere.

0.16

Version 2024-2 Page 7 of 108

Schedule A - Statement of Work

Requirement Comment Deduction

24. Project Management Bidder Box 4

Bidder must provide a Work Breakdown Structure (WBS) that corresponds with the milestone dates set forth above. The WBS must identify all State and Contractor responsibilities.

4.2 Cleanse and prepare data extracts –

Should be a combined effort for the data extract and for the lack of detail. "How" only and lacks visibility into dependencies, level of effort, and/or critical path.

2. Schedule A – Table 1 – Business Specification Worksheet The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies were noted:

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

1.5 The system must receive data from

Rhapsody and have views that allow administrators to monitor electronic message processing. The system must include a system monitoring and performance report or view for administrative users to access and review to identify areas where intervention is needed. System monitoring report must contain information such as message volume, the volume by condition, type, sender and accuracy.

They specify how accuracy is validated but not calculated.

0.15

Version 2024-2 Page 8 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

1.13 The system must allow the configuration

of exports in FHIR JSON, HL7 or XML format, consistent with CDC Message Mapping Guides (MMGs). Messages will be passed through Rhapsody to the CDC. When MMGs change with emerging issues and priorities, the modern system must allow administrative users to perform data quality checks and make modifications to the exports as needed.

Response lacks sufficient information about the rules engine. It does not explain how this requirement will be fulfilled using the rules engine or where the rules engine will reside. Specifically, additional details are needed on how the export rules engine will enable administrative users to define and manage mappings, transformations, and conditional logic through a user interface.

1.14 The system must allow administrative

users to set parameters for exports and reporting to the CDC by condition or report type either on a schedule or as needed.

Though they describe 'what' will be performed, they do not sufficiently answer 'how' the activities will occur (ex.

what technology).

0.15

3.3 The system must have the ability to

generate reports that use geospatial analysis (e.g. heat maps) to assist users in identifying non-routine clustering of cases geographically.

Bidder did not respond to requirement. 0.12

7.1 The system must allow for the creation

and maintenance of preliminary person-records (as part of contacts) that contain very minimal identifiable information.

Depending on the purpose of the person reported to the system (e.g., case, contact, preliminary person), the system must manage different types of data elements as set by business.

Bidder did not respond to requirement. 0.0937

Version 2024-2 Page 9 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

7.1.2 Preliminary person records must be able

to store investigatory data, must be modifiable, and must be searchable among all types of person records based on parameters defined by business, for example, first or last name, date of birth, associated HRSE.

Bidder did not respond to requirement. 0.0937

7.12.1 The system must be able to track the

location of a person (e.g., case, contact, potential contact) throughout a general facility including floor, unit, room number, bed, etc.

Bidder did not explain how requirement would be met.

0.0468

7.17.2 The system must support the automatic

classification of a contact record to a case when set criteria are met. The system must maintain the contact relationship (to the original person, exposure or HRSE) after the classification of the record to case status.

Bidder did not explain how automatic classification works?

0.0468

7.28 The system must allow select system

administrative users to manage the archiving and deletion of data based on retention schedules.

Bidder did not explain how requirement would be met.

0.0468

3. Vendor Questions Worksheet

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Version 2024-2 Page 10 of 108

Vendor Questions Worksheet

Requirement Comment Deduction

5a Experience 1 No mention of electronic health messaging, no prior experience with a DSS, dollar range suggests similar size, results hits on key success measures and timeline but does not describe scope, size and methodology. The answer is well thought out and detailed. Many of their project successes are relevant to this solicitation (limited downtime, modernization, end user/stakeholder engagement). No reference to development. Used structured SDLC processes, not an Agile approach.

5b Experience 2 No mention of electronic health messages, no DSS experience, dollar range does not suggest similar size, results obtained only mentioned key outcomes and timeline. Less detail provided, repetitive. Used structured SDLC processes, not an Agile approach.

5c Experience 3 No mention of electronic health messaging, No DSS experience, dollar range does not suggest similar size.

Results obtained does mention size, scope, methodology and key outcomes.

Version 2024-2 Page 11 of 108

4. Resume Templates The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Resume Templates

Requirement Comment Deduction

Role 1 Contractor Security Officer Contractor didn't list the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role in box provided.

0.25

Role 2 Contractor Project Manager Contractor lists the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role in the box provided.

0.25

Role 3 Contractor Technical Lead / Architect Contractor lists the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role in box provided.

Description doesn’t demonstrate any relevant agile practice during project execution.

1.5

Role 4 Contractor Agile Team Lead(s) (Scrum Master(s) or equivalent)

Contractor lists the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role in box provided.

Description doesn’t demonstrate any relevant agile practice during project execution.

Version 2024-2 Page 12 of 108

Resume Templates

Requirement Comment Deduction

Role 4 Contractor Product Manager Contractor lists the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role in box provided. No custom build PH experience.

0.25

Role 6 Contractor Lead Product Designer Contractor lists the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role in box provided.

0.25

Role 7 Contractor Quality Assurance Lead Contractor lists the skills and experience that qualify the individual for the duties and responsibilities on this project for the proposed role in box provided.

0.25

Total Score: 83.6922/100

B. Bidder # 2

The Evaluation Team determined that AHEAD, Inc., based on a score of 80.9982, did meet the requirements of this RFP.

This determination was accomplished by evaluating their responses to the Technical Evaluation Criteria.

1. Schedule A – Statement of Work The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Version 2024-2 Page 13 of 108

Schedule A - Statement of Work

Requirement Comment Deduction

4.IT ENVIRONMENT

RESPOSIBILITIES

Bidder Box 3

Bidder agrees to provide Maintenance, Support and Enhancements for the Modernized MDSS.

Tier 3 details are missing. SLA details (24 x 7 availability only for urgent incident, if required) are not in accordance with what is proposed in Schedule D.

0.25

6. USER TYPE AND

CAPACITY

Bidder Box 1

Bidder must provide details regarding latency response time for (i.e., Generate Page Load, standardized reporting, ad hoc reporting). The Bidder must identify what network connectivity, or equipment the State will be required to have to meet the expected latency response time?

Standardized Reporting: 5–10 -seems to be high

• Sufficient Network Bandwidth and Low Latency is not quantifiable

• Optimized Database Performance - is vendor responsibility. Proposed technology (Azure and .NET core) to handle latency and response time is not in alignment with the proposed MDSS 2.0 Architecture that was conveyed by SOM.

8. REQUIRED

FUNCTIONALITY RELATING

TO DATA RETENTION,

DISPOSAL, AND RETRIEVAL

Bidder Box 1

Bidder must review and explain how the data retention, disposal, and retrieval requirements will be met by the solution and describe its data management capabilities (storage limitations, duration, etc.). If the Solution does not allow the State to perform these activities itself, the bidder must explain how it will support the State’s compliance with these requirements.

Bidder did not explain how data retention, disposal, and retrieval requirements would be met.

0.5

Version 2024-2 Page 14 of 108

Schedule A - Statement of Work

Requirement Comment Deduction

9. END USER AND IT

OPERATING

ENVIRONMENT

Bidder Box 1

Bidder must describe any State system access requirements that are necessary for the Bidder to perform its obligations on a timely basis, including but not limited to, physical or remote access to State networks, servers, or individual workstations. Bidder must describe how it plans to manage and maintain the State IT environment.

Vendor assumptions/expectation of tech stack in dev and test environment of Azure SQL/ Cosmos DB / Azure Event Hubs is not in alignment with the envisioned MDSS 2.0 architecture that was conveyed by SOM.

0.5

9. END USER AND IT

OPERATING

ENVIRONMENT

Bidder Box 2

Bidder must describe if it can comply with the current environment and how it intends to comply with any future changes to the IT environment. And if not, describe what IT and end user operating environment its Solution supports.

Vendor proposal of .NET Core, C# is not in alignment with the current environment and as well future that is envisioned for MDSS

2.0 architecture as conveyed by

SOM.

0.5

10. SOFTWARE

Bidder Box 3

Bidder must identify any unique software requirements to full fill the terms of the Contract.

Does not mention software requirements here.

0.5

24. PROJECT

MANAGEMENT

Bidder Box 4

Bidder must provide a Work Breakdown Structure (WBS) that corresponds with the milestone dates set forth above.

The WBS must identify all State and Contractor responsibilities.

Light on who owns what and when it gets done.

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Version 2024-2 Page 15 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

1.1 The system must have FHIR, V2 & CDA

processing capability and be able to receive ELR and ECRs in FHIR JSON, HL7 or XML format.

The proposed approach is too general and lacks a clear action plan or implementation methodology

0.15

1.2 The system must have tools or

mechanisms that allow administrators to modify codes and rules that govern the import, mapping and interpretation of data once the data is ingested into MDSS. Codes and rules must be modified for processes such as duplicate record management, search, reporting and exports.

No tools or mechanisms. does not explain how the requirement will be fulfilled, offering only general assurance without supporting detail. Explanation lacks vision and tools on how admins will be provided capability to govern the rules.

0.15

1.3 No tools or mechanisms. does not

explain how the requirement will be fulfilled, offering only a general assurance without supporting detail.

Explanation lacks vision and tools on how admins will be provided capability to govern the rules.

The bidder states they will meet the requirement but does not provide sufficient detail on how administrators will set the logics – no tools mention. The response is lacking clarity on whether logic can be configured using specific data elements within the message payload.

Version 2024-2 Page 16 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

1.5 The system must receive data from

Rhapsody and have views that allow administrators to monitor electronic message processing. The system must include a system monitoring and performance report or view for administrative users to access and review to identify areas where intervention is needed. System monitoring report must contain information such as message volume, the volume by condition, type, sender and accuracy.

The vendor did not specify how accuracy is calculated or validated within the dashboard.

0.15

1.6 The system must be able to add new

sending facilities and update sending facility information for ELR and eCR reporting, capturing requisite sending facility information. A sending facility table will be accessed by Rhapsody for message onboarding and routing.

Bidder did not explicitly confirm that all requisite sending facility information will be captured and maintained in a structured table accessible to Rhapsody. lacks Details missing on how data fetched from API will be utilized for onboarding and routing.

0.3

1.7 To help facilitate better data quality, the

system must have a mechanism to send acknowledgement messages back to senders through Rhapsody.

The bidder did not specify the acknowledgment format or confirming alignment with sender expectations and Rhapsody standards.

Version 2024-2 Page 17 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

2.1 The system must identify potentially

duplicative information (ex: persons, cases, labs, HRSEs, etc) as it is processed electronically (through ELR, eCR, or manual entry into the system) and parse information that requires manual decision from information that can be determined automatically as matching and processed automatically.

Vendor referenced ED architecture but did not provide details on how they will achieve this requirement.

0.125

2.2 In addition to identifying duplicative

information as it is processed electronically, the system must have a mechanism to identify and resolve erroneously merged or duplicative information that has been stored in the database.

Not enough detail provided. 0.125

2.3.1 The system must be able to handle the

fluctuations in data sent to the system which can unbalance algorithms, and reprioritize data elements, so selected administrative users must have the ability to intervene and adjust algorithms as needed. Incoming data can be duplicative on multiple levels (person, case, lab result) so mechanisms to identify duplicates much address all levels.

Bidder did not explain how requirement will be met.

0.125

Version 2024-2 Page 18 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

2.4 The manual process to identify and

manage potentially duplicative records must be straightforward and efficient for users to implement. The system must present the user with all potential duplicate records and the necessary information to determine if the record in review is indeed a duplicate. The system must allow the user reviewing the potential duplicate to choose which value from each record should be part of the merged record.

Bidder did not provide enough details for how requirement will be met.

0.125

2.5 The system must make available a

report or view of the volume and type (manual or automated) of duplication matching performed for person, cases, and labs.

Bidder did not provide enough details for how requirement will be met.

0.125

7.1 The system must allow for the creation

and maintenance of preliminary person-records (as part of contacts) that contain very minimal identifiable information. Depending on the purpose of the person reported to the system (e.g., case, contact, preliminary person), the system must manage different types of data elements as set by business.

Bidder did not describe preliminary person records.

Version 2024-2 Page 19 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

8.1 The system must allow users to

perform person outreach through phone call communication, bidirectional email communication, and/or bidirectional text communication that integrates into state approved text messaging service.

Bidder did not explain how the requirement will be met or what tools will be used for outreach.

0.13

8.1.1 The system must allow users to

manually set groups of individuals to send communications to.

Bidder did not explain how the requirement will be met.

0.13

8.2 The system must engage the outreach

processes (bidirectional text, email, phone calls) to communicate with various entities (such as sending facilities, general facilities medical providers, schools, etc.) that are involved in public health investigations.

Bidder did not explain how the

0.13

Version 2024-2 Page 20 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

8.3 The system must provide user interface

to prioritize and schedule person outreach. The system must allow for automatic system prioritization and scheduling based on user defined business rules. The system must allow for end user directed prioritization as needed. Outreach is done for purposes such as to provide guidance information to individuals, to determine who else might be exposed, and to check on whether or not individuals develop symptoms in a set period of time post exposure. The system must allow the user to filter cases or contacts for priority outreach (examples of individuals that are higher priority could be those that are still in a window of time where post- exposure prophylaxis could prevent the onset of disease, or individuals that were exposed to highly infectious diseases).

The system must allow users to create prioritization rules based on condition, person, place and time.

Bidder did not explain how the

Version 2024-2 Page 21 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

8.3.1 The system must be configurable to

prioritize contact tracing based on a set of rules that may be unique to the circumstances under investigation. The system must allow users to create prioritization based on factors such as condition, proximity to symptom onset, and exposure. The system must be capable of automated contact tracing (i.e., SMS, Email) when there is a large volume of contacts.

Bidder did not explain how the requirement will be met.

0.13

8.3.2 The system must allow for automated

ingestion of incoming contact tracing/monitoring and outreach data into tables and mapping to corresponding data fields on outreach forms. The system must be configurable to trigger actions based on incoming outreach data. The incoming data elements and actions will be determined by system administrators and will depend on the HRSE.

Bidder did not explain how the

Version 2024-2 Page 22 of 108

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Vendor Questions Worksheet

Requirement Comment Deduction

5a Experience 1 Mentions work with FHIR and Interoperability across systems.

No DSS experience. Dollar value does not suggest a similar size.

Results obtained did not mention size of the project but went into good detail regarding scope, methodology and success factors. Phase 2 is not complete, so we cannot judge a finished project.

5b Experience 2 No mention of electronic health messaging, no DSS experience, no dollar value listed. Results obtained was detailed and mentioned size, scope, some methodology and success factors.

3.5

Version 2024-2 Page 23 of 108

Vendor Questions Worksheet

Requirement Comment Deduction

5c Experience 3 No mention of electronic health messaging, no DSS experience, no dollar value listed. Results obtained was detailed and mentioned size, scope, some methodology and success factors.

4. Resume Templates The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Resume Templates Requirement Comment Deduction Role 2 Contractor Project Manager No explicit government work, but following strict gov restrictions like FDA

0.25

Role 3 Contractor Technical Lead / Architect Public Health and MDSS specific alignment is missing for Architect.

Role 4 Contractor Product Manager No public health experience. 0.5

Version 2024-2 Page 24 of 108

Resume Templates Requirement Comment Deduction Role 6 Contractor Lead Product Designer Number of years of experience stated from 06/2022 - Present - Only qualifies 3 years. Other experience highlighted doesn't show relevant experience in Product Design.

Total Score: 80.9982/100

C. Bidder # 3

The Evaluation Team determined that CDW Government LLC., based on a score of 92.1869, did meet the requirements of this RFP. This determination was accomplished by evaluating their responses to the Technical Evaluation Criteria.

1. Schedule A – Statement of Work The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies were noted:

Schedule A - Statement of Work

Requirement Comment Deduction

7. ACCESS

CONTROL AND

AUTHENTICATION

Bidder Box 1

Bidder must explain how they will meet the requirements for Access Control and Authentication.

RBAC related authorization controls not explained very well.

Version 2024-2 Page 25 of 108

Schedule A - Statement of Work

Requirement Comment Deduction

9. END USER AND

IT OPERATING

ENVIRONMENT

Bidder Box 1

Bidder must describe any State system access requirements that are necessary for the Bidder to perform its obligations on a timely basis, including but not limited to, physical or remote access to State networks, servers, or individual workstations. Bidder must describe how it plans to manage and maintain the State IT environment.

Bidder did not describe how it plans to manage and maintain the State IT environment.

0.5

24. PROJECT

MANAGEMENT

Bidder Box 4

Bidder must provide a Work Breakdown Structure (WBS) that corresponds with the milestone dates set forth above. The WBS must identify all State and Contractor responsibilities.

Basic response - very simple, no detail. No milestone date correspondence.

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Version 2024-2 Page 26 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

1.3 Message interpretation may vary by

condition and requires using different criteria to set rules or logic (e.g., determining case status or determining merge logic). The system must allow administrators to set logic based on specific data elements in addition to report type (manual, ELR, eCR, etc.), and report source (healthcare organization) criteria. Incoming messages contain a variety of types of data, both relating to persons and relating to cases.

They identify in a detailed way that the system will do those things but don’t say how.

0.15

1.13 The system must allow the configuration

of exports in FHIR JSON, HL7 or XML format, consistent with CDC Message Mapping Guides (MMGs). Messages will be passed through Rhapsody to the CDC. When MMGs change with emerging issues and priorities, the modern system must allow administrative users to perform data quality checks and make modifications to the exports as needed.

Response lacks detail on process, roles, and tools.

0.15

2.1.1 The system must leverage information

available in the State of Michigan (SOM) Master Person Index (MPI) during the processing of incomplete ELR and ECR records to augment person demographic data, create more complete records in

Bidder did not explain how they will fully meet this requirement.

Version 2024-2 Page 27 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction the MDSS, and support duplicate detection.

3.7.1 The system must have the ability to

report on the timeliness of actions taken towards investigation completion and performance metrics. For example, reporting on all cases for an investigator and the time from case reported to case resolved.

Too generic of an answer and does not provide enough detail.

0.06

5.1.2 The system must allow notes to be

included in case history logs and audit reports for transparency and traceability.

Did not state "how" they'll meet this requirement.

0.1

7.1.2 Preliminary person records must be able

to store investigatory data, must be modifiable, and must be searchable among all types of person records based on parameters defined by business, for example, first or last name, date of birth, associated HRSE.

Bidder did not include an in depth description of system design to meet this requirement.

0.0468

7.4 The system must be able to

automatically create and link preliminary and complete person records as contacts to cases or HRSEs from outreach data received and ingested from surveys, text messages, etc., based on the criteria set by business.

Bidder did not explain how outreach data ingested would be used to associate complete or incomplete records.

Version 2024-2 Page 28 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

7.9.2 The system must implement an auto

save feature for inputted notes and give users the option to manually save as well.

Bidder did not explain how their auto save mechanism work.

0.0468

7.11.1 The system must allow administrative

users to determine a standard set of fields that transfer between record types.

This ensures accurate transfer of data during creation of records.

Bidder does not explain how the field transfer tools will work.

0.0468

7.12.5 The system should enable identification

of exposure sites within the general facilities.

Bidder did not specify their proposed tools for tracking exposure sites within the facility

0.0468

7.16.1 The system must allow for administrative

users to set criteria to meet an HRSE definition. Examples to data elements used to set criteria may include time, symptoms, exposure and test results.

Bidder did not specify how admins will set the criteria to meet HRSE definition.

Version 2024-2 Page 29 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

7.17.1 The system must allow a user to classify

cases or contacts based on questionnaire responses. Questionnaire responses might identify that an individual met exposure or symptom criteria set by a case definition. The system must allow the user to set criteria which will automatically trigger (initiate) an MDSS case once selected exposure information is met by an individual, and/or link that individual to a HRSE.

The bidder does not address how questionnaire responses will be used in record classification or how admins can enable this automatic classification.

0.0468

7.17.3 The system must allow for the creation of

contacts from an uploaded list of contacts and their identifying information.

Bidder doesn't address the need for a bulk upload of contacts.

0.0937

Version 2024-2 Page 30 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

7.26 The system must allow administrative

users to manage sending facilities by organization level, facility level and geographic area. Facility tables must represent the hierarchy of reporting systems (ex: organizations, hospitals, laboratories, congregate groups, outpatient reporting facilities, and other reporters). To assure data quality, a mechanism is needed to vet, manage and verify senders of electronic messages. The system must obtain and maintain up to date contact information (e.g. emails) from sending facilities.

Bidder did not discuss facility tables and how they represent the hierarchy of reporting systems.

Version 2024-2 Page 31 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

8.3 The system must provide user interface

to prioritize and schedule person outreach. The system must allow for automatic system prioritization and scheduling based on user defined business rules. The system must allow for end user directed prioritization as needed. Outreach is done for purposes such as to provide guidance information to individuals, to determine who else might be exposed, and to check on whether or not individuals develop symptoms in a set period of time post exposure. The system must allow the user to filter cases or contacts for priority outreach (examples of individuals that are higher priority could be those that are still in a window of time where post-exposure prophylaxis could prevent the onset of disease, or individuals that were exposed to highly infectious diseases).

The system must allow users to create prioritization rules based on condition, person, place and time.

Does not address the scheduling of outreach communications.

0.13

8.5.3 The system must allow users to edit

generated documents before distribution. Final documents must also be printable for mailing as needed.

Does not mention the ability to print. 0.13

Version 2024-2 Page 32 of 108

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Vendor Questions Worksheet

Requirement Comment Deduction

5a Experience 1 No mention of electronic health messaging, NBS is a DSS similar to MDSS on a national level. Details mentioned size, scope, methods, and success factors.

5b Experience 2 No mention of electronic health messaging, NBS is a DSS similar to MDSS. The dollar value is within range to suggest similar size.

Details mentioned size, scope, methods, and success factors. The answer repeated itself a lot and used acronyms without definition which made some parts confusing to read.

5c Experience 3 Mentions ELR and HL7 work. NBS is a DSS similar to MDSS. The dollar value does not suggest a project of similar size. The results obtained mentioned size, scope, methods, and success factors.

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Version 2024-2 Page 33 of 108

Resume Templates

Requirement Comment Deduction

Role 1 Contractor Security Officer Lacks demonstration of technical/core skills and tool expertise. No NIST Security Controls, State security control exposures.

Less experience than expected.

0.75

Total Score: 92.1869/100

D. Bidder # 4

Bidder #4 Conduent Public Health Solutions, Inc. has not met the requirement of being responsive due to submitting a bid for 240000002761 not 250000002570.

Version 2024-2 Page 34 of 108

E. Bidder # 5

The Evaluation Team determined that Deloitte Consulting LLP, based on a score of 90.4578, did meet the requirements of this RFP. This determination was accomplished by evaluating their responses to the Technical Evaluation Criteria.

1. Schedule A – Statement of Work The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies were noted:

Schedule A - Statement of Work

Requirement Comment Deduction

6. USER TYPE AND

CAPACITY

Bidder must provide details regarding latency response time for (i.e., Generate Page Load, standardized reporting, ad hoc reporting). The Bidder must identify what network connectivity or equipment will the State be required to have to meet the expected latency response time?

Standard reporting and Adhoc reporting -page load time missing.

No bandwidth requirements provided Requirements from vendor not clear.

0.25

10. SOFTWARE

Bidder Box 7

Bidder must explain the responsive design implementation that will be compatible with the Solution for all mobile devices.

Bidder solution is only partially responsive on desktop devices and not responsive on mobile devices at all.

11. INTEGRATION

Bidder Box 4

Queuing Plat form(like KAFKA)(Future integration)

Kafka is better suited for cloud-native, event-driven architectures. IBM MQ is more aligned with traditional enterprise middleware and may require additional effort to scale or integrate with modern platforms.

Version 2024-2 Page 35 of 108

Schedule A - Statement of Work

Requirement Comment Deduction

12. MIGRATION

Bidder Box 3

Bidder must also explain how the proposed Solution’s environment can scale up or down without affecting performance. Bidder must provide the cost for such migration in their cost proposal.

Bidder did not provide cost for migration. 0.5

25. UI/UX Design Bidder Box 1

Describe your methodology to UI/UX Design for this project., including how it is organized, the deliverables to be produced, the tools that will be leveraged in the process, and how the process can be sustained over time.

UI/UX limited for form and field tweaks.

Remain JSF framework that we no longer use in modern design. also mixed UI with JSF for old modules and new in Next.js

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

1.1 The system must have FHIR, V2 & CDA

processing capability and be able to receive ELR and ECRs in FHIR JSON, HL7 or XML format.

No mention of FHIR JSON. 0.15

Version 2024-2 Page 36 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

2.1.4 The system must provide alternative

processes for duplicate management depending on record source (ex: ELR, eCR, or manual entry) to accommodate for differences in data availability.

Bidder didn't fully explain how they would handle the different record sources to meet this requirement.

0.125

3.1.4 The system must allow users to search

and report on all data fields, inclusive of surveys, questionnaires and any ad hoc data fields created for cases and HRSEs.

Bidder does not provide sufficient detail. 0.06

5.2 System must have audit logging

capabilities, capturing user level or role level changes.

Bidder did not describe how the requirement will be met.

0.1

5.3 System must have centralized log

management. System must capture API calls and other resource logs. System must capture system-initiated transactional event and audit logs from the environment, application, and database so that it will be centralized for efficient analysis and search.

Bidder did not explain how transactional events will be handled.

0.1

7.9.2 The system must implement an auto

save feature for inputted notes and give users the option to manually save as well.

Bidder did not address auto-save feature. 0.0468

Version 2024-2 Page 37 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

7.1 In the creation of a new record from an

existing one, the system must maintain the original record for future reference.

For example, when a case is made from a contact, the original contact record must not be lost.

Bidder did not explain how they would meet this requirement.

0.0468

7.17 The system must provide flexibility for

administrative users to set and change individuals' relationship to a HRSE. The system must allow administrative users to reclassify cases and contacts when additional information becomes available. Once criteria are set for a HRSE, the system must automatically determine if a contact or case meets (or no longer meets) those predefined criteria.

Bidder did not address admin users' ability to set/change relationships to an

HRSE.

0.0468

7.18.3 For types of HRSE, the system must

allow users a mechanism to create the HRSE and store information regarding it, with flexibility to tailor the needed information.

Bidder did not fully explain how they would handle this requirement.

0.0468

8.5.2 The system must allow the creation of

documents and letters templates that autofill key contact information to be customized for personal distribution.

Bidder did not address the creation of documents and letters templates.

Version 2024-2 Page 38 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

8.5.3 The system must allow users to edit

generated documents before distribution. Final documents must also be printable for mailing as needed.

Bidder did not address the requirement. 0.26

8.5.4 The system must allow users to track

and view the distributed material from the Document Library associated with the case, contact, general facility, sending facility or event.

Bidder did not explain how the requirement will be met.

0.13

9.2 The system must provide a method for

offline person record creation and linking as a new case, contact, preliminary person, or HRSE. The system must have the ability to sync with the live system once a connection is available.

Bidder did not respond to requirement. 0.4

9.3 The system must support responsive

design principles to ensure a seamless user experience across various screen sizes.

Bidder did not respond to the complete responsive design for various screen sizes.

0.2

Version 2024-2 Page 39 of 108

Schedule A – Table 1 – Business Specification Worksheet

Requirement Comment Deduction

9.5 The system must allow for multiple

people to access and edit records simultaneously. When an outbreak investigation is underway, there is a need for multiple individuals to work the outbreak and update records simultaneously. The system must notify users when additional users are modifying the same record.

The Bidder response does not fully meet the States need.

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Requirement Comment Deduction

5a Experience 1 Explicitly mentions work with ecr and elr.

This is a DSS. Its OTS but mentions customization for the state. Dollar value is just under the dollar range to suggest similar size. Results obtained mentions all key components. Answer is clear and detailed.

Version 2024-2 Page 40 of 108

Vendor Questions Worksheet

Requirement Comment Deduction

5b Experience 2 Mentions use of MMG. This is an OTS dss but did undergo some level of customization. Results obtained missed details on methodology. Style point:

repeated a lot of the same points without more elaboration.

5c Experience 3 They mention ELR, eCR, MMG, and data integration, they also customized a disease surveillance system, lower than dollar value range, clearly stated the results obtained and provided details.

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Resume Templates

Requirement Comment Deduction

Role 1 Contractor Security Officer Percentage time allocated 10% 0.25

Role 2 Contractor Project Manager Project Management Professional or Product Owner Certification.

0.25

Role 3 Contractor Technical Lead / Architect The percentage of time allocated to the resource is 25%. Experience description not showing the skills that we would like to see.

0.25

Role 4 Contractor Agile Team Lead(s) (Scrum Master(s) or equivalent)

This person is listed for both this position and Product Manager.

Version 2024-2 Page 41 of 108

Resume Templates

Requirement Comment Deduction

Role 4 Contractor Product Manager This person is listed for both this position and Agile Team Lead.

0.75

Role 6 Contractor Lead Product Designer Candidate meets 5 year requirement and has public heath exposure. But the UX certifications listed are UI Path, Databricks, MicroStrategy, Salesforce are nothing to do with UI/UX and more on the plaform certificates. Salesforce UX strategy is only one relevent. Hands on UI/UX Scope is less on Power platform and Salesforce.

Total Score: 90.4578/100

F. Bidder # 6

The Evaluation Team determined that Effectual Inc., based on a score of 74.1386, did not meet the requirements of this RFP. This determination was accomplished by evaluating their responses to the Technical Evaluation Criteria.

1. Schedule A – Statement of Work The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Version 2024-2 Page 42 of 108

Schedule A - Statement of Work

Requirement Comment Deduction

4. IT ENVIRONMENT

RESPOSIBILITIES

Bidder Box 3

Bidder agrees to provide Maintenance, Support and Enhancements for the Modernized MDSS.

Critical issues - within 30 minutes during core business hours. Bidder did not agree to support critical and high issues 24/7.

0.25

4. IT ENVIRONMENT

RESPOSIBILITIES

Bidder Box 4

Bidder must provide their plan and staffing model for the Maintenance and Support period.

M & O, calls for Preventive Maintenance and Corrective Maintenance to be managed by SOM and supported by vendor. Resource time allocation is very limited.

and does not match the size/scope of the project

0.5

7. ACCESS CONTROL

AND

AUTHENTICATION

Bidder Box 1

Bidder must explain how they will meet the requirements for Access Control and Authentication.

RBAC related authorization controls not explained very well.

0.25

8. REQUIRED

FUNCTIONALITY

RELATING TO DATA

RETENTION,

DISPOSAL, AND

RETRIEVAL

Bidder Box 1

Bidder must review and explain how the data retention, disposal, and retrieval requirements will be met by the solution and describe its data management capabilities (storage limitations, duration, etc.). If the Solution does not allow the State to perform these activities itself, the bidder must explain how it will support the State’s compliance with these requirements.

Not explained in detail how the solution does retention, disposal and retrieval.

0.75

Version 2024-2 Page 43 of 108

Schedule A - Statement of Work

Requirement Comment Deduction

16.

DOCUMENTATION

Bidder Box 1

Bidder must provide details on, and examples of, documentation to meet the requirements set forth in this section.

No manuals proposed, no examples provided, pretty light from a documentation standpoint

0.25

24. PROJECT

MANAGEMENT

Bidder Box 1

The Bidder is required to provide their plan of using Agile methodology as they will apply it to MDSS Modernization. The plan should include the description of which agile ceremonies will be used, how backlog will be developed and maintained, the agile development metrics that they would track, and methods for measuring progress.

Light on details. No ceremony descriptions, no backlog management description, no development metrics, no methods for measuring progress.

The Evaluation Team determined that overall, the responses were mostly satisfactory, but the following deficiencies

Schedule A – Table 1

– Business Specification Worksheet

Requirement Comment Deduction

1.1 The system must have FHIR, V2 & CDA

processing capability and be able to receive ELR and ECRs in FHIR JSON, HL7 or XML format.

The bidder’s response lacks sufficient detail regarding how the requirement will be met. Specifically, no tools or processes have been identified to demonstrate their approach.

Version 2024-2 Page 44 of 108

Schedule A – Table 1

– Business Specification Worksheet

Requirement Comment Deduction

1.2 The system must have tools or

mechanisms that allows administrators to modify codes and rules that govern the import, mapping and interpretation of data once the data is ingested into MDSS. Codes and rules must be modified for processes such as duplicate record management, search, reporting and exports.

Missing the tools or mechanisms that allows administrators to modify codes and rules…