Schedule G Section 2 Software Table.xlsx
XLSX spreadsheet 24 KB Posted
- Solicitation number
- RFP-171-250000002307-2
- Issued by
- Grand Traverse County, Lansing City, Michigan
About this file
This document is a Schedule G Section 2 Software Table from Request for Proposal (RFP) No. 250000002307, appearing to be for the State of Michigan's technology procurement process. The table is a comprehensive software requirements matrix designed for potential contractors to detail their proposed software solutions for various portal and system needs, including Plan Sponsor Portal, Member Portal, Contractor to Provider Portal, and Claim Processing System. The document requires bidders to provide extensive details about their software offerings, including user types, access levels, estimated user numbers, mobile responsiveness, access control, authentication mechanisms, hosting arrangements, and data management capabilities.
The software table demands thorough technical specifications, focusing on scalability, performance, network connectivity requirements, mobile device compatibility, and hosting environments. Bidders must explicitly describe their data center locations, data storage methods, potential use of subcontractors, and compliance with state data management requirements. The document emphasizes the need for comprehensive information about software functionality, potential add-on modules, system integration capabilities, and the ability to adapt to changing state business or technical demands. Critical areas of focus include end-user operating environments, authentication protocols, and data retention, disposal, and retrieval capabilities, suggesting a rigorous evaluation process for selecting a technology solution that meets the state's complex operational needs.
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. 250000002307 | |||||||||||||||||||||||||||||||
| Bidders must complete all columns for all Software. 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 | |
| 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) | |
| 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. Bidder's response must include but not be limited to the required features specified in Schedule A Section 1.5.8 | |
| Section 2.7 Access Control and Authentication | Bidder must explain how they will meet the requirements for Access Control and Authentication. |
| Section 2.8 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.10 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 explain if any portion is provided by a Permitted Subcontractor as defined in Hybrid Contract Terms. |
Bidder must ensure that subcontractor information here correlates with response in Schedule A Section 4.15 Disclosure of Subcontractors.
Also indicate if there is any Third Party or open source code.
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.15 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.15 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.11 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 .