Att F - Technical Proposal.docx
DOCX document 33 KB Posted
- Solicitation number
- 26-85939
- Issued by
- Marion County, Indiana
About this file
This is a Technical Proposal Attachment document for RFP 26-85939, requesting a Learning Management System (LMS) solution. The respondent must provide detailed descriptions addressing eleven core technical requirements sections: LMS User Access and User Accounts, Training Content, Course Management, Scheduling and Rollout Functions, LMS User Notifications, Assessments, Tracking and Reporting, Migration and Historical Data, Technical Support, Hosting, and Compliance with relevant standards. Additionally, respondents must articulate their company's assumptions and constraints related to the scope of work and available state resources.
The document serves as a structured template for vendors to document how their proposed solutions will meet each specified requirement, with provisions for attachments that clearly reference the relevant sections and questions they address. The proposal format requires responses in designated blue-shaded areas and mandates comprehensive documentation of all supporting materials.
View the file
Other files
Show all 27
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-85939
TECHNICAL PROPOSAL
ATTACHMENT F
INSTRUCTIONS
· Please supply requested information in the blue-shaded areas and indicate any attachments that have been included.
· Document all attachments with which section and question they pertain to.
Technical Proposal Questions
1. LMS User Access and LMS User Accounts: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section LMS User Access and LMS User Accounts from the Scope of Work document for this RFP.
2. Training Content: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section 2. Training Content from the Scope of Work document for this RFP.
3. Course Management: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section 3. Course Management from the Scope of Work document for this RFP.
4. Scheduling and Rollout Functions: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section 4. Scheduling and Rollout Functions from the Scope of Work document for this RFP.
5. LMS User Notifications: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section 5. LMS User Notifications from the Scope of Work document for this RFP.
6. Assessments: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section 6. Assessments from the Scope of Work document for this RFP.
7. Tracking and Reporting: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section 7. Tracking and Reporting from the Scope of Work document for this RFP.
8. Migration and Historical Data: The Respondent must provide a description regarding how it will meet and address the requirements shared in 8. Migration and Historical Data from the Scope of Work document for this RFP.
9. Technical Support: The Respondent must provide a description regarding how it will meet and address the requirements shared in 9. Technical Support from the Scope of Work document for this RFP.
10. Hosting: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section 10. Hosting from the Scope of Work document for this RFP.
11. Compliance with IOT: The Respondent must provide a description regarding how it will meet and address the requirements shared in Section 11. Compliance with IOT from the Scope of Work document for this RFP.
12. Other Considerations:
13. General Overall Assumptions: What assumptions and constraints have your company made in responding to the technical proposal. This should include assumptions made based on the scope of work outlined in the RFP and assumptions regarding the resources available from the State for this scope of work.
Attachment F, Page 2 of 2
File details come from the government source that posted it. Updated .