Schedule N Section 2 Solutions Table.xlsx
XLSX spreadsheet 22 KB Posted
- Attached to
- HMO Services for MPSERS
- Solicitation number
- RFP 171 230000003226 2
- Issued by
- Michigan
About this file
This is a Schedule N Section 2 Solutions Table for RFP No. 230000003226 issued by the State of Michigan, establishing required submission criteria for bidders proposing solutions to this procurement opportunity. The document outlines 30 specific columns of information that bidders must complete for all proposed solutions, covering solution identification, user access specifications, performance capabilities, and technical infrastructure requirements. Required information includes the solution name, type of user access, estimated and concurrent user numbers, scalability and performance metrics, latency response times, network connectivity requirements, and a comprehensive description of the solution including name, type, version, release number, and contractor services being provided.
Bidders must additionally address mobile responsiveness by providing a list of compatible devices and performable features, end-user operating environment requirements including state system access needs and compliance capabilities, and detailed hosting arrangements specifying all data center locations where state data will be stored. The submission must clarify whether solutions are cloud-based or on-premise hosted, identify any subcontractor involvement in data storage or hosting, and describe the ability to support the original environment throughout the contract term. Bidders are required to explain how they communicate roadmap changes, identify necessary plug-ins for system requirements, and detail how customers collaborate in decision-making processes for upgrades and maintenance. Optional add-on modules and the solution's ability to scale rapidly according to changing state business or technical demands must also be addressed.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Schedule B Pricing.xlsx | XLSX spreadsheet | |
| Schedule I2 PPO Medicare Summary of Benefits.pdf | ||
| Schedule I4 Medicare Prescription Drug Summary of Benefits.pdf | ||
| Schedule F Definitions.docx | DOCX document | |
| Schedule G - Contractor Performance Evaluation Survey.doc | DOC document | |
| Schedule I1 PPO Non Medicare Summary of Benefits.pdf | ||
| Schedule K 834 Use Case and Example.docx | DOCX document | |
| Schedule M HMO Census Data REVISED.xlsx | XLSX spreadsheet | |
| Schedule J Dependent Coverage.pdf | ||
| Schedule P TRR Report Template.xlsx | XLSX spreadsheet | |
| Schedule L Benefit Comparison and Actuarial Attestation.xlsx | XLSX spreadsheet | |
| Schedule H HMO Benefits Summary and Claims Paid Data.xlsx | XLSX spreadsheet | |
| Schedule I3 Non-Medicare Prescription Drug Summary of Benefits.pdf | ||
| 230000003226 HMO Services RFP.docx | DOCX document | |
| 230000003226 Questions Answers.pdf | ||
| Schedule Q RFI Report Template.xlsx | XLSX spreadsheet | |
| Schedule R Payment Discrepancy Report Template.xlsx | XLSX spreadsheet |
Show all 17
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
| SCHEDULE N - SECTION 2 SOLUTIONS TABLE | |||||||||||||||||||||||||||||||
| RFP NO. 230000003226 | |||||||||||||||||||||||||||||||
| Bidders must complete all columns for all Solutions. | |||||||||||||||||||||||||||||||
| Required Solution Information per Schedule A, Section 2. | |||||||||||||||||||||||||||||||
| # | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | |
| Section 2.6 | Name of Solution | ||||||||||||||||||||||||||||||
| Type of User | |||||||||||||||||||||||||||||||
| Access Type | |||||||||||||||||||||||||||||||
| Estimated Number of Users | |||||||||||||||||||||||||||||||
| Number of Concurrent Users | |||||||||||||||||||||||||||||||
| How will it be able to support the expected number of concurrent Users: | |||||||||||||||||||||||||||||||
| Explain whether the Solution can scale up or down without affecting performance: | |||||||||||||||||||||||||||||||
| Provide details regarding latency response time for (i.e., Generate Page Load, standardized reporting, ad hoc reporting): | |||||||||||||||||||||||||||||||
| Identify what network connectivity or equipment will the State be required to have to meet the expected latency response time: | |||||||||||||||||||||||||||||||
| Description of Solution including but not limited to: Name, type, version, release number, etc.), | |||||||||||||||||||||||||||||||
| Solution functionality and Contractor’s services (what service(s) the Contractor is providing through this solution) | |||||||||||||||||||||||||||||||
| Optional Add-On Modules | |||||||||||||||||||||||||||||||
| Solution’s ability to be rapidly configured or scaled as the State’s business or technical demands change | |||||||||||||||||||||||||||||||
| Section 2.4 Mobile Responsiveness | Bidder must provide a list of all mobile devices that are compatible with the Member-Facing Solution(s). | ||||||||||||||||||||||||||||||
| Bidder must list the features that can be performed via a mobile device. | |||||||||||||||||||||||||||||||
| Section 2.7 End-User Operating Environment | 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 if it can comply with the current environment and how it intends to comply with any future changes to the user environment. And if not, describe what end user operating environment its Critical System Solution(s) support: | |||||||||||||||||||||||||||||||
| Bidder must describe if it can support the original environment throughout the term of the contract: | |||||||||||||||||||||||||||||||
| Bidder must describe how it communicates changes to its roadmaps: | |||||||||||||||||||||||||||||||
| Bidder must identify any plug-ins necessary for the proposed Critical System Solution(s) to meet the system requirements of this request: | |||||||||||||||||||||||||||||||
| Bidder must describe how customers collaborate with your organization in the decision-making process for upgrades, maintenance, and change control: | |||||||||||||||||||||||||||||||
| Section 2.9.2 Hosting | Bidder must explain their hosting arrangements and include all Data center locations where State Data will be stored: Bidder must indicate where all data (any and all State Data and information including but not limited to provider portals, member portals, State of Michigan system access/portal, and claims or eligibility or related information or data) under this Contract would be stored (e.g., cloud-based solution, on-premise/physical data center) and include city, state, and detail. | ||||||||||||||||||||||||||||||
| Bidder must explain if any portion is provided by a subcontractor. Bidder must ensure that subcontractor information here correlates with response in Schedule A Section 4.2.6 Disclosure of Subcontractors: |
File details come from the government source that posted it. Updated .