Schedule G Section 2 Software Table.xlsx
XLSX spreadsheet 25 KB Posted
- Solicitation number
- RFP 171 260000002410 2
- Issued by
- Michigan
About this file
Schedule G Section 2 Software Table Summary
This is a software products and services schedule document associated with Michigan's Behavioral Health and Substance Use Disorder Benefits Administration contract opportunity. The Schedule G Section 2 Software Table appears to detail software solutions and related services required to support behavioral health and substance use disorder benefits administration functions. The document serves as a comprehensive catalog or requirements matrix identifying specific software applications, modules, or tools necessary for the administration of behavioral health benefits, including potential quantity specifications, functionality requirements, and integration needs aligned with the state's benefits administration objectives.
The document provides detailed pricing and configuration information for software solutions within the benefits administration system. This schedule likely includes cost structures, licensing terms, implementation timelines, and technical specifications for various software components or vendors participating in the competitive process. The information contained in this table would inform pricing proposals, vendor selection criteria, and the overall cost analysis for system implementation and ongoing operational support of the behavioral health and substance use disorder benefits administration platform in Michigan.
View the file
Other files
Show all 19
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 G - SECTION 2 SOFTWARE TABLE | |||||||||||||||||||||||||||||||
| RFP NO. 260000002410 | |||||||||||||||||||||||||||||||
| Bidders must assign each proposed Software (also may be described as software/portals/Hosted Services/Solutions/SaaS/open-source/third party products/components/cloud-based/etc.) its own column and complete the required information in ROWS 6 through 36, leaving no cells blank. Bidder to insert more columns if needed. | |||||||||||||||||||||||||||||||
| Required Software Information per Schedule A, Section 2. | Plan Sponsor Portal | Member Portal | Contractor to Provider Portal | Claim Processing System (internal to Contractor) | Other | Other | Other | ||||||||||||||||||||||||
| # | 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 | Plan Sponsor Staff | Member | Provider | Contractor Staff | |||||||||||||||||||||||||||
| Access Type | Read Only | ||||||||||||||||||||||||||||||
| Estimated Number of Users | 25 | Refer to Schedule A, Background Section for Member estimates |
| Number of Concurrent Users (multiple users accessing the Software simultaneously) |
| How will it be able to support the expected number of concurrent Users: |
| Explain whether the Software 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 the State will be required to have to meet the expected latency response time: |
| Description of Software including but not limited to: Name, type, version, release number, etc.), |
| Software functionality and Contractor’s services (what Contract Activity(s) the Contractor is providing through this Software) |
| Identify and describe any use of artificial intelligence (AI) within the proposed Software/open source/third-party products. |
In addition, please indicate if the AI use is optional, and the State has discretion to opt out(disable functionality)
| Optional Add-On Modules | |
| Software'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 Software. |
| Bidder must list the features that can be performed via a mobile device. See also Schedule A Section 1.6.7.1 | |
| 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 Software supports: | |
| 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 Software 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 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/Software, on-premise/physical data center) and include city, state, and detail. |
| Bidder must disclose if any portion of the Software is provided by a subcontractor or Permitted Subcontractor as defined in Hybrid Contract Terms. Bidder must also disclose if any subcontractors are used to support the software or host infrastructure. |
Subcontractors include any third party the Contractor uses to perform Contract Activities for the State under the Contract. Parent or subsidiary companies that will perform Contract Activities under the Contract must be included as subcontractors. If a subcontractor is using any third party to perform Contract Activities, they must be included as subcontractors.
Bidder must ensure that subcontractor information discussed here correlates with response in Schedule A Section 4.9 Disclosure of Subcontractors.
| Indicate if there is open source code or other third party products |
| Indicate whether this is a Software, Service, or Software and Service that is utilized in providing services under this Contract (Select Software, Service, Software and a Service, or N/A for each) |
(NOTE: "Software" and "Software and Service" must be disclosed in this Schedule G; "Service" and "Software and Service" must be disclosed in Schedule A, Section 4.9 Disclosure of Subcontractors.)
Does the Software or Service provider Access, Process, or store State Data under this Contract (Select YES, NO, or N/A for each) (Refer to the State's definition of State Data in Hybrid Contract Terms) For extra clarity, member data is also State Data, even new member data created between member and provider(vision doctor) and provider(vision doctor) and Contractor.
| If "Service" or "Software and a Service" was selected in ROW 30, please indicate if a 3rd party is providing the service (Select YES, NO or N/A for each) |
| If YES was selected in ROW 32, please identify/disclose who. |
Note: Bidder must ensure that the entity (subcontractor) information here correlates and is also provided within the response in Schedule A Section 4.9 Disclosure of Subcontractors.
If "Service" or "Software and a Service" was selected in ROW 30, please confirm technical detail has been provided/accounted for it, in Bidder's provided Disaster Recovery Plan.
Section 2.10 Required Functionality Relating to Data Retention, Disposal, and Retrieval 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.
File details come from the government source that posted it. Updated .