Att F - Technical Proposal I-SEAL RFP.docx

DOCX document 46 KB Posted

Attached to
I-SEAL 2027 Indiana Special Education Alt LicenseBid Documents
Solicitation number
26-87473
Issued by
Marion County, Indiana

About this file

This is a Technical Proposal Instructions document for RFP 26-87473 I-SEAL 2027 Indiana Special Education Alt License, issued by the State of Indiana. The RFP solicits a vendor to develop and implement a comprehensive special education alternative licensing program. Vendors must respond to thirteen scope of work questions addressing primary partner programs, eligibility requirements, scholarship assistance programs, technology infrastructure, completion testing support workshops, project timelines, project responsibilities and deliverables, state requirements, and solution configurability. The document requires vendors to confirm their ability to meet Indiana's timeline and describe quality control processes for all deliverables. Vendors must also address specific inquiries regarding artificial intelligence utilization in both the proposed solution and development processes, including disclosure of whether AI tools were used in proposal preparation.

The proposal instructions emphasize the State's preference for out-of-box functionality and configuration options over customization, with customization permitted only when necessary to meet federal or state requirements, security mandates, system integration needs, or when demonstrating material service improvements. All customizations require written Project Steering Committee approval before implementation and must include comprehensive documentation including configuration analysis, functional specifications, technical design, impact analysis, test plans, rollback plans, and itemized pricing. Vendors must provide source code, developer and user documentation, and perpetual royalty-free licenses for custom code. Additionally, vendors must confirm conformance with Indiana's Assistive Technology Standard and State architectural standards, provide incident response process documentation, outline equipment needs with reimbursement understanding, and disclose all artificial intelligence technologies used in proposal development.

View the file

Other files

File Type Posted
RFP Addendum 1.pdf PDF
Att C - Indiana Economic Impact Form - updated.xls XLS spreadsheet
RFP Boilerplate Document-rtp 2.pdf PDF
Att E - Business Proposal-updated.docx DOCX document
Att B - Sample Contract - updated.docx DOCX document
Att J - Attestation Form - updated.docx DOCX document
Att K - Scope of Work-RTP.docx DOCX document
Att A1 - IVOSB-rtp.docx DOCX document
Att E - Business Proposal-rtp.docx DOCX document
Copy of Copy of Att D - Cost Proposal I-SEAL RFP.xlsx XLSX spreadsheet
Att B3 - IOT-SaaS.docx DOCX document
Att H - Reference Check Form-rtp.docx DOCX document
Att A - MWBE-rtp.docx DOCX document
RFP Boilerplate Document-rtp.pdf PDF
Att B1 - IOT-IaaS.docx DOCX document
Artificial Intelligence - Technical Proposal Questions.docx DOCX document
Att B2 - IOT-PaaS.docx DOCX document
Att I - Pre-proposal Network Form-rtp.docx DOCX document
Att K - Scope of Work-RTP.pdf PDF
Infrastructure Overview.docx DOCX document
Att G - Q&A Template-rtp.xlsx XLSX spreadsheet
Att C - Indiana Economic Impact Form.xls XLS spreadsheet
Att B - Sample Contract.docx DOCX document
Att J - Attestation Form.docx DOCX document
Show all 24

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

RFP 26-87473 I-SEAL 2027 INDIANA SPECIAL EDUCATION ALT LICENSE

TECHNICAL PROPOSAL QUESTIONS

ATTACHMENT F

Instructions: Vendor should provide a document formatted with Question #, RFS SOW Section, and Response Area followed by the vendor’s narrative response to that question. The response must address all items detailed below and provide the information and documentation as required. The response must be structured to address each question listed below. A table of contents (see “Section 2. Table of Contents”) must also be completed as listed in this Attachment. Where appropriate, supporting documentation may be referenced by a page and paragraph number. However, when this is done, the body of the Technical Proposal must contain a meaningful summary of the referenced material. The referenced document must be included as an appendix to the technical proposal with referenced sections clearly marked. If there are multiple references or multiple documents, these must be listed and organized for ease of use.

Scope of Work Questions

Question #
SOW
Response Area(s)
1.1
2.0 Primary Partner Programs
The Respondent must describe how they will meet the requirements listed in section 2.0 of the Scope of Work.
1.2
3.0 Eligibility
The Respondent must describe how they will meet the requirements listed in section 3.0 of the Scope of Work.
1.3
4.0 Scholarship Assistance Program
The Respondent must describe how they will meet the requirements listed in section 4.0 of the Scope of Work.
1.4
5.0 Technology
The Respondent must describe how they will meet the requirements listed in section 5.0 of the Scope of Work.
1.5
6.0 Completion Testing Support Workshop
The Respondent must describe how they will meet the requirements listed in section 6.0 of the Scope of Work.
1.6
7.0 Project Timeline
The Respondent must confirm their ability to meet the timeline described in section 7.0 of the Scope of Work. If the vendor wishes to propose any adjustments to the timeline, they should do so here and explain how those changes would benefit the project.
1.7
8.0 Project Responsibilities/Deliverables of the respondent
The Respondent must describe how they will meet the requirements listed in section 8.0 of the Scope of Work. The Respondent should also describe the QC processes they have in place to ensure all work and deliverables will be high quality and defect free.
1.8
9.0 State Requirements
The respondent must confirm that they are able to meet the requirements listed in section 9.0 State Requirements and describe how each requirement will be met.
1.9
5.0 Technology

8.0 Project Responsibilities/Deliverables

Solution Incorporating AI:

· Does the proposed solution utilize any form of artificial intelligence (AI), as defined by IC 4‑13.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.

· 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.

1.10
9.0 State Requirements
Does the application conform to the Assistive Technology Standard, within the State’s Information Security Framework (https://www.in.gov/iot/iot-vendor-engagement/), State Assistive Technology (https://www.in.gov/core/accessibility.html), and the State’s architectural standards? If not, is there a plan to migrate the application to conform to the Assistive Technology Standard and/or the State’s architectural standards in a timeline that is agreeable to all parties?

Will your company develop and maintain the application to conform to the Assistive Technology Standard and the State’s architectural standards, unless both your company and the State agrees to why that is not possible?

Will your company create a plan and manage the activities to migrate the application to conform to the Assistive Technology Standard and/or the State’s architectural standards in a timeline that is agreeable to all parties?

1.11
9.0 State Requirements
Provide incident response process documentation covering ticketing, escalation, timelines for State notification, and reporting of resolved incidents including root cause analysis and lessons learned for major incidents.
1.12
9.0 State Requirements
Outline equipment needs (if any), including, but not limited to the quantity, specifications, etc. If equipment is needed to access the State’s network, confirm you understand the requirement to reimburse the State for equipment and access‑related costs per the Indiana Office of Technology Services Catalog rates.
1.13
8.0 Project Responsibilities/Deliverables
Solution Configurability and Customization Preference:

· The State prefers a solution that meets requirements in the following priority order: out of the box functionality; configuration; or customization only as a last resort. The State expects the selected vendor to act as a partner to help identify potential business process changes that leverage out of the box or configuration options and reduce or eliminate the need for custom code. To help facility this, the selected vendor must document the out of the box and configuration options evaluated before proposing any customization and must demonstrate why configuration cannot satisfy the requirement.

· Customizations should be considered only when one or more of these criteria apply: the requirement is necessary to meet a federal reporting requirement or regulation; the requirement is necessary to meet a state law, regulation, or rule; the requirement is necessary to satisfy state security requirements; the requirement is necessary to interface or integrate with state systems; or the requirement will produce a material improvement in service delivery, partner interactions, or utilization of state resources. Material improvements must be documented, justified, and presented to the Project Steering Committee for review.

· All customizations require written approval from the Project Steering Committee before work begins. Each customization proposal must include a configuration first analysis, a functional specification, a technical design, an impact analysis addressing maintenance, upgrade compatibility, security, performance, accessibility, total cost of ownership, a test plan, a rollback plan, schedule impact, and itemized pricing if applicable. Approved customizations must pass the same acceptance tests as core functionality, be upgrade compatible or provide a documented migration path, and meet State security standards. The vendor will deliver source code, developer and user documentation, and a perpetual royalty free license for any custom code. Additionally, the State expects the vendor to consider approved and implemented customizations for incorporation into the selected vendor core solution going forward so that they become out of the box functionality

Section 2: Table of Contents Instructions: After responding to all questions above, vendor should add page numbers for each question/response.

Section 1: Scope of Work Questions

Question #
Response Page #

1.1

1.2

1.3

1.4

1.5

1.6

1.7

1.8

1.9

1.10

1.11

1.12

1.13

Section 3: Additional Technical Requirements

Artificial Intelligence (AI) Use Disclosure

· The State seeks to understand the use of artificial intelligence tools in the preparation of vendor submissions. Respondents must disclose whether AI technologies were used in developing any portion of their proposal.

· AI Utilization Statement

· State whether any AI tools or systems were used in drafting, reviewing, or generating any part of this proposal.

· Description of Use If AI was used, provide the following details:

· Identify which sections, questions, or deliverables within the proposal were created, reviewed, or influenced by AI tools.

· Describe the purpose for using AI (e.g., drafting assistance, grammar review, data analysis, summarization).

· Explain the extent of human review and validation applied to AI‑generated content to ensure accuracy, completeness, and compliance with solicitation requirements.

AI Tools and Data Sources

· List the AI tools or platforms used (e.g., generative text tools, code assistants, data‑analysis models).

· Describe any datasets, proprietary information, or third‑party content provided to the AI tools during proposal development.

File details come from the government source that posted it. Updated .