Attachment_G.pdf
PDF 188 KB Posted
- Attached to
- Ordering Services
- Solicitation number
- 2000018465
- Issued by
- Mower County, Minnesota
About this file
This is a Technical Questions attachment for a Request for Proposal (RFP) issued by the State of Minnesota Department of Human Services for ordering services supporting the Minnesota Sex Offender Program (MSOP) at Moose Lake and St. Peter Correctional Facilities. The RFP seeks contractors to provide ordering services and products along with adequate staffing for customer service, order execution, order support, and contract management. The State reserves the right to award multiple contractors if deemed in the State's best interest. Prospective responders must submit written questions by the end of day July 20, 2026, to jennifer.bartle@state.mn.us, with responses provided via addendum. Responses must be submitted through the Supplier Portal by the deadline specified in the Event Details, with technical support available through the SWIFT Vendor Helpline at 651.201.8100, Option 1. All RFP attachments, sample contract, and exhibits must be reviewed and completed by responders prior to submission.
The Technical Questions attachment requires detailed responses across eight categories addressing application and database support (Oracle Database or MS SQL Server), system hosting arrangements (DHS, Contractor, or Hybrid), scalability and modularity, software licensing requirements, security compliance with State of Minnesota Enterprise Information Security Policies and Standards, system maintenance and disaster recovery capabilities including zero downtime goals, installation and update procedures, detailed hardware specifications, and accessibility features. Responders must address requirements related to Microsoft Server 2025 compatibility, MNIT Private Azure Cloud server configuration support, user interface design, remote access capabilities, backup and recovery processes, change management protocols, support response times, and strategies for ensuring accessible digital technology throughout the project lifecycle. Points will be awarded based on the evaluation criteria outlined in Section 5 of the main RFP document (Event 18465_RFP_C-1154), with responses to these technical questions potentially affecting the overall proposal score if not adequately addressed.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Ordering_Services.pdf | ||
| Event_18465_RFP_Attachments_C-1154.pdf | ||
| Exhibit_D_Price_Schedule_Event_18465.xlsx | XLSX spreadsheet | |
| Event_18465_RFP_C-1154.pdf | ||
| Event_18465_RFP_SampleContractandExhibits_C-1154.pdf |
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
ATTACHMENT G: TECHNICAL QUESTIONS
Responders are required to answer the following technical questions (attach additional page(s) if necessary). If no response(s) are submitted for these questions, points may not be awarded. See Section 5: Evaluation Procedure and Criteria in Event 18465_RFP_C-1154 document for the maximum amount of points available for this attachment.
1. APPLICATION/DATABASE
1.1 Indicate which of the third-party backend databases listed below is supported by the responder’s proposed system:
• Oracle Database
• MS SQL Server
Describe in detail the systems available.
2. SYSTEM
2.1 Who will host the system, DHS, Contractor or Hybrid? Describe the technology requirements is hosted by DHS or Hybrid.
2.2 Identify any system requirement that requires the State to purchase interfaces from third-party vendors to work with the proposed solution.
2.2 Define the scalability of the proposed system. Can the system be purchased in modules and be expanded? How scalable is the proposed software regarding the number of users?
2.3 Identify if the proposed system software is Open Database Connectivity (ODBC), Open Linking and Embedding (OLE) or Online Analytical Processing (OLAP) compliant.
2.4 Describe the operating system proposed with the system.
2.5 What is the bandwidth recommendation for use with the proposed system?
2.6 What is the expected life (in years) of the proposed system?
3. SOFTWARE
3.1 Identify how many users per application server are supported by the proposed software.
3.2 List and describe the licenses required for the system software (concurrent/per seat and the number associated).
3.3 Identify all additional software licensing requirements for all interfaces.
4. SOFTWARE SECURITY
4.1 Use the following State of Minnesota Enterprise Information Security Policies and
Standard’s documents as guidelines to show how your proposed solution/product meets The State of Minnesota security and network firewall requirement.
https://mn.gov/mnit/assets/enterprise-physical-environmental-security-policy_tcm38- 323786.pdf https://mn.gov/mnit/assets/Network%20Security%20Standard_tcm38-323785.pdf
4.2 Use the following State of Minnesota Enterprise Information Security Policies and Standard’s document as a guideline to show how your proposed solution/product meets The State of Minnesota authentication and authorization protocol for users, user roles, group and password requirements.
https://mn.gov/mnit/assets/Identity%20and%20Access%20Management%20Standard_tcm38- 323781.pdf
4.3 What are the secure login and audit trail capabilities of the proposed system?
4.4 What are the levels of authentication available with the proposed system?
4.5 What are the test environment requirements with the proposed system?
https://mn.gov/mnit/assets/enterprise-physical-environmental-security-policy_tcm38-323786.pdf https://mn.gov/mnit/assets/enterprise-physical-environmental-security-policy_tcm38-323786.pdf https://mn.gov/mnit/assets/Network%20Security%20Standard_tcm38-323785.pdf https://mn.gov/mnit/assets/Identity%20and%20Access%20Management%20Standard_tcm38-323781.pdf https://mn.gov/mnit/assets/Identity%20and%20Access%20Management%20Standard_tcm38-323781.pdf
4.6 Describe the remote access capabilities used by the proposed system (VPN, etc.), including how remote support is provided. Include information on how your staff will access the system.
4.7 How does the system support web integration (client/server, thin client, web interface)?
5. SYSTEM MAINTENANCE
5.1 Describe the Disaster Recovery plan which is to include the State’s goal of zero downtime.
5.2 Describe the notification provided to the State if a system failure occurs, including major and minor hardware and software issues. What log reports and historical information can be provided to the State?
5.3 Describe the process for automatic restarting service after a failure due to hardware, software or absence of power.
5.4 Describe the backup capabilities for the proposed system.
5.4.1. What is the process for how backups are performed?
5.4.2. What information is backed up?
5.4.3. What is the frequency of incremental and full backups?
5.5 Describe your firm’s process for change management or customer notification within the proposed system.
5.6 Describe how your firm can provide application and system support.
5.7 What is the average response time for maintenance and support requests?
5.8 Provide the company escalation and response plan and describe how issues are triaged and escalated.
6. INSTALL/UPDATES
6.1 The Contractor will be required to provide system documentation (online, hard copy, etc.). Detail how documentation is provided to the State for the initial implementation as well as future updates and releases.
6.2 What is the process for how critical updates are installed? Will it be handled by your staff, State staff, or some other method?
6.3 What solutions are provided for the bulk loading of user and other information during setup or conversion from legacy to new solution system?
7. HARDWARE
7.1 Provide detailed hardware specifications, including but not limited to, server footprint, processor type and speed, RAM (in the basic system), size of the hard drive, type of monitors (with or without readers), barcode devices, scanning devices, barcode printing devices, RFID devices, etc. Include the recommended number of devices per location and recommended number of backup devices.
8. MISCELLANEOUS
8.1 Describe the use of thin-client to be used by the proposed system and indicate if it is fully supported.
8.2 Describe the user interface. How will users interact with the system? For example, will it be all touch screen or a screen with adjacent buttons? Will there be audio output? A keyboard option?
8.3 Confirm if all components that will run on State of Minnesota servers can support Microsoft Server 2025 running in a MNIT Private Azure Cloud server configuration. If server(s) are required, is the proposed system compatible with being run in a virtual Azure server environment and hosted on State infrastructure? If no, why not?
8.4 Describe how you ensure your staff and Contractors have the knowledge and skills to create accessible digital technology within the scope of the project or services requested within this solicitation.
8.5 Describe your approach to ensuring accessibility for your solution (e.g., strategy, tools, design, testing, ongoing validation).
8.6 Include if/how you incorporate accessibility into your development process (e.g., requirements, design, development, testing, maintenance, bug prioritization).
8.7 Include how you ensure accessibility post implementation (e.g., future enhancements).
File details come from the government source that posted it. Updated .