79415Addendum 2.docx
DOCX document 101 KB Posted
- Attached to
- Central Reservations SolutionBid Documents
- Solicitation number
- RFP 25-79415
- Issued by
- Grant County, Indiana
About this file
This document is Addendum #2 for a Request for Proposal (RFP 25-79415) issued by the Indiana Department of Administration on behalf of the Department of Natural Resources for a Central Reservations Solution. The solicitation seeks a comprehensive reservation management system with a revised submission due date of June 4, 2025, at 3:00 PM ET. Key milestone dates have been updated, including the deadline for written questions (March 21, 2025) and responses to questions (April 4, 2025). The addendum introduces new attachments and modifies existing sections, with particular emphasis on requirements related to artificial intelligence (AI) utilization and cloud-based service offerings.
The addendum includes detailed requirements for vendors regarding AI usage, developer practices, and cloud hosting preferences. The State of Indiana strongly prefers a cloud-based solution using a state-owned cloud tenant (Microsoft Azure or Amazon Web Services), with vendors required to demonstrate compliance with NIST 800-53, Revision 5 security standards. Vendors must provide comprehensive details about their AI implementation, development practices, and cloud hosting strategy, including potential impacts on solution functionality and development processes. The procurement seeks a flexible, technologically advanced reservation system that can handle multiple facility types and operational needs, with the state maintaining significant oversight and control over the technological implementation.
View the file
Other files
Show all 35
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
STATE OF INDIANA
ADDENDUM #2
Request for Proposal 25-79415
INDIANA DEPARTMENT OF ADMINISTRATION
On Behalf Of Department of Natural Resources
Solicitation For:
Central Reservations Solution
Submission Form Due Date and Time:
May 28, June 4, 2025 @ 3:00 PM ET
Christina Garcia, Procurement Consultant cgarcia@idoa.in.gov Indiana Department of Administration Procurement Division 402 W. Washington St., Room W468 Indianapolis, Indiana 46204
Summary of Changes Deletions are indicated via strikethrough and additions have been made in red font in the corresponding documents.
I. The following edits have been made to the RFP Main Document:
1.24 Summary of Milestones
Key Dates
| Activity |
| Date |
| Issue of solicitation |
| Febrary 28, 2025 |
| Deadline to Submit Written Questions |
| March 14 21, 2025 |
by 3:00 PM Eastern Time
| Deadline to Submit Pre-Proposal Networking Forms |
| March 14 21, 2025 |
| Response to Written Questions/Amendments |
| March 28 April 4 , 2025 |
| Deadline to Submit Round 2 Written Questions |
| April 11, 2025 |
| Response to Round 2 Written Questions |
| April 29, 2025 |
Submission Due Date/Time
May 21 28, 2025 June 4, 2025 by 3:00 PM Eastern Time
Submission of Reference Check Forms to State
May 21 28, 2025 June 4, 2025 by 3:00 PM Eastern Time
1.5 Solicitation Outline
| Attachment C |
| Indiana Economic Impact Form |
| Attachment D |
| Cost Proposal Template |
| Attachment E |
| Business Proposal Template |
| Attachment F |
| Technical Proposal Template |
| Attachment F1 |
| Scope of Work |
| Attachment F2 |
| INDNR CRS Business Rules for 2024-2026 |
| Attachment F3 |
| INDNR POS Active Product List |
| Attachment F4 |
| INDNR Locations for Hardware and Connectivity List |
| Attachment G |
| Q&A Template |
| Attachment H |
| Reference Check Form |
| Attachment I |
| Pre-proposal Network Opportunities Form |
| Attachment J |
| Attestation Form |
| Attachment K |
| Cloud Questionnaire |
| Attachment L |
| Assistive Technology Compliance Evaluation Form |
| Attachment M |
| Resource Usage Template |
| Attachment N |
| Infrastructure Overview Attachment |
II. A new document has been added: Attachment N Infrastructure Overview has been added.
III. The following edits have been made to Attachment F Technical Proposal
2.4.11.10 Does the proposed solution utilize any form of artificial intelligence (AI), as defined by IC 4-12.1-5-1 (https://iga.in.gov/laws/2024/ic/titles/4#4-13.1-5-1)? If so, please address the following:
· How is AI utilized within the solution?
· Can the AI functionality be disabled without impacting the overall functionality or performance of the proposed solution?
· Can the State enable/disable the AI functionality, or is that controlled by the solution/implementation provider?
· If disabling AI does result in limitations, please specify what those limitations are.
· Is there a plan to introduce AI into the solution in the next four (4) years if AI is not already utilized OR is there a plan to expand AI in the solution if AI is already utilized?
If AI is not currently used in the proposed solution AND there are no plans currently to add AI to the proposed solution, respond with confirmation of understanding in the response area below.
2.4.11.11 Do your developers use artificial intelligence (AI), as defined by IC 4-12.1-5-1 (https://iga.in.gov/laws/2024/ic/titles/4#4-13.1-5-1) to augment their work? If so, please address the following:
· Describe the degree to which your developers use AI to augment their work.
· Describe the extent to which AI tools for development work are proposed for use in this project.
· Can the AI functionality be disabled without impacting the development of the proposed solution?
· If disabling AI does impact the development of the proposed solution, please specify what those impacts are.
· Is there a plan to introduce AI as part of the development of the proposed solution in the next four (4) years if AI is not already utilized in development OR is there a plan to expand AI as part of the development if AI is already utilized?
If AI is not currently used by developers and there are no plans currently to leverage AI as part of development during the project or in Maintenance & Operations, respond with confirmation of understanding in the response area below.
2.4.12.5 The State strongly prefers a cloud-based service offering within a state-owned cloud tenant. However alternative solutions may be considered if they demonstrate significant value. Please see the Infrastructure Overview Attachment of the RFP for detailed requirements information.
Cloud-Based Service Offering:
Any cloud-based solution recommended by vendors should use a State of Indiana-owned cloud tenant. The State of Indiana will establish an appropriate cloud tenant for the solution as part of the design activities early in the project. The vendor is expected to install, update, and manage the application and other unique aspects of the solution during the project to meet State of Indiana requirements and as part of Day 2 support / Maintenance and Operations. The State of Indiana requires the receipt of the 1) financial consumption charges as part of the usage within the State of Indiana owned cloud tenant and 2) visibility into the security results throughout the life of the solution on the State of Indiana owned cloud tenant.
If your company is recommending an exception to using a State of Indiana owned cloud tenant as described in the Infrastructure Overview Attachment of the RFP, provide a clear justification for why hosting within a state-owned cloud tenant is not feasible and describe your company's status and readiness for compliance with NIST 800-53, Revision 5 (or the current version at the time of proposed solution go-live).
Outline, in detail, your company's overall cloud-based service strategy, specifying:
· the hosting location
· your company’s agreement with the financial consumption and security visibility expectations if your company is recommending a solution hosted in a State of Indiana owned cloud tenant
· your company’s NIST 800-53, Revision 5 readiness if recommending a solution that is not hosted in a State of Indiana owned cloud tenant.
Identify any assumptions made in your company’s response and provide a detailed explanation for each assumption to ensure a clear and mutual understanding of the proposed solution.
If proposing a on-premises service offering, respond with “N/A” in the response area below.
[Cloud-Based Service Offering Response Area]
On-Premises Service Offering:
If proposing an on-premises service offering, please describe your approach to delivering on-premises-based services for the two scenarios outlined in the Infrastructure Overview Attachment of the RFP. Include details on how your solution will address the scope of services, service levels, and costs as defined in the “Hosting” section of the IOT-Services-Catalog.pdf. Additionally, provide examples of similar projects your company has successfully implemented to demonstrate your capability.
Identify any assumptions made in your company’s response and provide a detailed explanation for each assumption to ensure a clear and mutual understanding of the proposed solution.
If proposing a cloud-based service offering, respond with “N/A” in the response area below.
[On-Premises Service Offering Response Area]
The State prefers a cloud-based service offering however it is willing to consider additional options that bring demonstrated value to the State. If the Contractor proposes a cloud-hosted solution, the State expects the Contractor to use a State-owned Microsoft Azure or Amazon Web Services (AWS) cloud tenant, unless the Contractor can provide compelling reasons and justification as to why hosting in a State-owned cloud tenant is not feasible. The State will consider those reasons and justification, but it is not required to agree with the Contractor’s cloud hosting option. However, if the State agrees with the Contractor’s cloud hosting solution that does not use a State-owned cloud tenant, the Contractor is required to:
demonstrate independently verified compliance with NIST 800-53, Revision 5 or the current version OR demonstrate a plan that uses independent verification of your path toward compliance with NIST 800-53, Revision 5 or the current version at the time of solution go-live.
Outline, in detail, your overall cloud-based service strategy that includes the hosting location (State-owned cloud tenant or another location) as indicated above. If recommending hosting the solution outside of a State-owned cloud tenant, supplement with details about your status of NIST 800-53, Revision 5 readiness as indicated above.
image1.jpg
File details come from the government source that posted it. Updated .