The vendor is required to provide software enhancements, upgrades and ongoing support to its educator information system (EIS).
- Specific will include:
1) Administrative rule related system updates
2) Modernize user interface and ADA compliance
3) Improve bureau workflow
 4) Upgrade the underlying data structures on an ongoing basis
 5) Create a reporting mechanism that allows department administrator(s) to generate reports for a dashboard, without individual report customizations (fy26)
• Expand EIS capabilities to provide financial projections
• Leverage EIS to provide email or text updates before and during the renewal process to encourage and facilitate educator license renewal
• Work with the credentialing staff to review the verification of certificates for educator working without an SOE.
• Work with department to explore the possibility to share criminal background check summary information with districts, if allowed per department rules.
• Expand on current EIS functionality to allow for enhanced communication with educators. EIS should allow for department staff to send emails from within EIS, to be sent from the system with a ‘do not reply’ configuration.
• Additionally, the EIS manager should be able to create templates that are emailed based upon actions within the system.
• a series of actions should be preconfigured so that the admin can initiate templates in the future, based upon those actions.
• The vendor should work across divisions within the department to ingrate EIS with other systems. for example, integrating EIS with the seeds (common database) to automate EIS security access based upon seeds roles.
• Additionally, the vendor should work to review and update collections across the department divisions to ensure the reporting of educator positions are accurate.
• Include considerations of how credentialing requirements can create reporting inconsistencies.
the vendor should recommend data collection standardizations, to improve reporting.
• The vendor will initiate a transition to update the system architecture and user interface for a subset of the educator information system, allowing for existing integration, and beginning with agreed upon functionality - likely the educator experience vendor should use .net, angular and typescript technologies.
• Improvement in this upgrade should include improved customer experience such as 1-step renewal applications and moving the selection of endorsement earlier in the application process.
• The architecture of EIS to manage application requirements should be refactoring.
• Additionally, the requirements for tests may need to be updated to meet legislative changes regarding reading pedagogy.
• The vendor should work with the credentialing staff to integrate ESP with EIS for data collections. for example, enabling the critical shortage survey to include existing educator counts.
• These counts can ensure supplied data is more accurate given the counts of existing state credentialed educators.
• The vendor will support the existing clearance review process to identify and implement improvements - for example, ability to see old applications, ability for direct email and ability to add requirements to an email template.
• The vendor will provide a report output option that allows for data visualization, creating graphs and charts of report data.
- Questions/Inquires Deadline: March 07, 2025