Schedule G Section 2 Software Table.xlsx
XLSX spreadsheet 22 KB Posted
- Solicitation number
- RFP - 171 - 240000001469
- Issued by
- Ingham County, Lansing City, Michigan
About this file
This document is an Excel file titled "Schedule G Section 2 Software Table" related to RFP No. 240000001469 for Workers Compensation Administration Services issued by the State of Michigan. The RFP is seeking information on software and technology requirements to support the administration of workers compensation claims, including details on software functionality, user access, scalability, latency response time, mobile responsiveness, access control and authentication, end-user operating environment, and hosting arrangements. The contract opportunity involves Ingham County and the City of Lansing. Bidders are required to provide detailed information for each software product proposed, including the name, type, version, release number, functionality, and contractor services. Bidders must also address specific technical requirements such as mobile device compatibility, access control, and hosting.
The RFP also includes instructions for submitting questions and proposals, as well as details on the upcoming question deadline and submittal process. No information is provided on pricing, set-asides, incumbents, funding requirements, or other financial terms. The contract term and renewal options are not specified in the documents provided.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Proposal Instructions Vendor Questions Worksheet.docx | DOCX document | |
| Schedule B - Pricing.xlsx | XLSX spreadsheet | |
| Schedule F File Layout.doc | DOC document | |
| IRS Publication 1075.pdf | ||
| Schedule A Statement of Work.docx | DOCX document | |
| Schedule C Insurance Requirements.docx | DOCX document | |
| Exhibit 7 Safeguarding Contract Language.pdf | ||
| Hybrid Contract Terms.docx | DOCX document | |
| Schedule D Service Level Agreements for Hybrid Purchases.docx | DOCX document | |
| 240000001469 WC Questions Answers.pdf | ||
| Department of Treasury Safeguard Requirements of Confidential Tax Data.doc | DOC document | |
| Schedule E Data Security Requirements for Hybrid Purchases.docx | DOCX document | |
| Schedule H Service Availability Report.xlsx | XLSX spreadsheet |
Show all 13
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. 240000001469 | |||||||||||||||||||||||||||||||
| Bidders must complete all columns for all Software. | |||||||||||||||||||||||||||||||
| Required Software 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 Software | ||||||||||||||||||||||||||||||
| 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 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 will the State 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. | |||||||||||||||||||||||||||||||
| Section 2.7 Acces 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.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/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.11 Disclosure of Subcontractors. Also indicate Third Party or open source. |
File details come from the government source that posted it. Updated .