OJA_LMS_RFP_Bidder_Response_Table_05.12.26.xlsx
XLSX spreadsheet 36 KB Posted
- Attached to
- Learning Management System
- Solicitation number
- EVT0010854
- Issued by
- Sedgwick County, Kansas
About this file
This is a bidder response table for a Learning Management System (LMS) request for proposal issued by the Kansas Supreme Court Office of Judicial Administration (OJA). The RFP seeks qualified vendors to provide a comprehensive LMS capable of delivering various types of training content including onboarding materials, policies and procedures, security awareness training, software training, judicial education, and professional development. The system must support multiple content formats (text-based modules, video, documents, assessments, recorded training), SCORM-compliant packages, and third-party learning content libraries. Key functional capabilities required include course creation and management, searchable course catalogs, user self-enrollment, training transcript maintenance, instructor-led training event management with attendance tracking, role-based access controls, reporting and analytics on training completion and participation, and the ability to record external training activities. The LMS must be accessible via standard web browsers to authorized users including KJB staff, judicial officers, contractors, attorneys, municipal court personnel, and other OJA-designated users, with support for secure external access without requiring connection to the internal network.
The successful bidder must provide implementation services including project management, system configuration, user data import, administrator and end-user training, and comprehensive documentation. The vendor is required to deliver a cloud-hosted, U.S.-based solution with single sign-on integration with Microsoft Entra ID, multi-factor authentication support, audit logging capabilities, and compliance with OJA's Information Security Requirements and Accessibility Addendum. The vendor must provide standard business hour support (Monday-Friday, 7:00 a.m. to 6:00 p.m. Central Time) with a 99.999% uptime requirement, defined service level agreements for issue response, and a non-production test environment for user acceptance testing. The bidder must commit to providing an "evergreen" LMS product with standard updates, security patches, and bug fixes included at no additional charge throughout the contract term and any renewals, and must proactively ensure compliance with applicable laws with required changes implemented no later than 30 days before the effective date of new regulations.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Learning_Management_System.pdf | ||
| EVT0010854_-_RFP_Document.pdf | ||
| Bid_Amendment_-_EVT0010854_-_Bid_Amendment_1.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
Instructions
| INSTRUCTIONS FOR BIDDERS |
| 1. Complete all tabs and all rows. Do not delete, reorder, or modify rows or columns. |
| 2. For Scope of Services (Section 4.3) and Services to be Provided (Section 4.4), provide a narrative response and select whether the proposed solution meets the requirement: Yes, Partial, or No. |
| 3. For Functional Requirements (Section 4.5), indicate how each requirement is met, such as standard functionality, configuration, integration, or another method, and provide supporting comments as needed. |
| 4. For Technical Requirements (Section 4.6), indicate whether each requirement is met and provide comments explaining the proposed approach, configuration, limitation, or dependency. |
| 5. If any requirement is only partially met or cannot be met, clearly explain the limitation, any workaround, and any proposed alternative approach. |
| 6. Do not leave any required fields blank. If a requirement does not apply, enter “N/A” and provide an explanation. |
| 7. For Security and Compliance Requirements (Section 4.7) and Additional Contractual Requirements (Section 4.8), bidders must indicate whether they can meet each requirement. If unable to meet a requirement, bidders must state “UNABLE TO MEET” and explain the limitation or proposed exception. |
Scope (4.3)
| Section | Requirement | Bidder Response | Meets (Y/P/N) | Notes |
| 4.3.A.i | The LMS shall support delivery of training content including onboarding materials, policies and procedures, security awareness training, software training, and training required under Kansas Supreme Court rules, applicable federal and state statutes, as well as judicial education, professional development, and policy-based training initiatives. | |||
| 4.3.A.ii | The LMS shall support import and delivery of recorded training content, including webinar recordings, and allow such content to be assigned, tracked, and included in user training records. | |||
| 4.3.A.iii | The LMS shall support upload, import, delivery, and access to OJA-provided training content in commonly used formats, including text-based modules, video, documents, assessments, recorded training content, and other training materials. | |||
| 4.3.A.iv | The LMS shall support industry-standard e-learning content formats, including Shareable Content Object Reference Model ("SCORM") packages. The LMS shall allow authorized users to import and deliver SCORM-based training modules and support standard SCORM data elements such as learner progress, assessment results, and time spent within the module. | |||
| 4.3.A.v | The LMS shall enable authorized users to create, modify, and manage training content within the system. | |||
| 4.3.A.vi | The LMS shall provide a searchable course catalog that allows users to browse and enroll in available training. | |||
| 4.3.A.vii | The LMS shall allow authorized users to assign, manage, and track training activities, including completion status, participation, and related training records for each user. | |||
| 4.3.A.viii | The LMS shall support creation of training records or learning activities that do not require hosted course content and allow such activities to be assigned, tracked, and reported in the same manner as other assigned training. | |||
| 4.3.A.ix | The LMS shall provide access to third-party learning content libraries, either natively within the system or through existing, supported integrations available at the time of proposal. | |||
| 4.3.A.x | The LMS shall allow users to browse, search, and enroll in third-party content through the LMS user interface without requiring separate authentication or navigation outside the system. | |||
| 4.3.A.xi | The LMS shall support inclusion of third-party content within the course catalog and ensure that such content is tracked within user training records, including completion status and related activity data. | |||
| 4.3.A.xii | Bidders must identify any third-party content providers available through the proposed solution and describe the nature of the integration, including whether such integrations are native, pre-configured, or require additional configuration. | |||
| 4.3.A.xiii | Any integration with third-party content providers must be available and operational at contract start and shall not require custom development, configuration, or integration effort by OJA. Any required setup shall be performed by the bidder as part of implementation services. | |||
| 4.3.A.xiv | Bidders must identify any third-party content included with the LMS and any additional licensing or subscription costs required to access such content. | |||
| 4.3.B.i | Users shall be able to view assigned training and track completion status. | |||
| 4.3.B.ii | Users shall be able to access previously completed training and training records. | |||
| 4.3.B.iii | The LMS shall provide role-based dashboards for learners and administrators. | |||
| 4.3.B.iv | The LMS user interface shall support accessibility standards consistent with the requirements defined in the OJA Accessibility Addendum. | |||
| 4.3.C.i | Authorized users shall be able to create and manage instructor-led training events within the LMS. | |||
| 4.3.C.ii | The LMS shall support event scheduling, location information, virtual meeting information, and capacity limits, as applicable. | |||
| 4.3.C.iii | The LMS shall support participant registration and enrollment for instructor-led training. | |||
| 4.3.C.iv | The LMS shall support recording of attendance and completion for instructor-led training. | |||
| 4.3.C.v | Completion of instructor-led training shall be recorded within the learner’s training record alongside other training activities. | |||
| 4.3.C.vi | The LMS shall support the creation, collection, and reminder notifications for feedback or evaluations related to instructor-led training. | |||
| 4.3.D.i | Authorized administrators shall be able to review training status by individual and organizational unit. | |||
| 4.3.D.ii | The LMS shall support reporting on training participation, completion, and related training activities. | |||
| 4.3.D.iii | The LMS shall maintain user training records and support administrative tracking of assigned, completed, overdue, and external training activities. | |||
| 4.3.D.iv | The LMS shall support reporting on evaluation results, including the ability to generate aggregated and anonymous reports across training activities. | |||
| 4.3.D.v | The LMS should provide advanced analysis capabilities for evaluation results, including automated summarization, identification of trends, and extraction of common themes or feedback points (e.g., strengths, areas for improvement), where such functionality is available. | |||
| 4.3.E.i | Authorized administrators shall be able to manually record completion of external training activities. | |||
| 4.3.E.ii | External training completion shall be recorded within the learner’s training record. | |||
| 4.3.E.iii | The LMS shall support import of external training records using standard system functionality where available. | |||
| 4.3.E.iv | The LMS shall support user submission of external training records, including the ability to enter training details and upload supporting documentation in various formats. The system shall include an approval workflow that allows authorized administrators to review, approve, or reject submitted records. Approved external training shall be recorded within the user’s training record and available for tracking and reporting. | |||
| 4.3.F | The LMS shall support role-based access controls that allow authorized administrators to define roles, assign users to roles, update role assignments, and restrict access to system features, content, data, and administrative functions based on assigned permissions. | |||
| 4.3.G.i | Authorized users may include KJB staff, judicial officers, contractors, attorneys, municipal court personnel, and other users designated by OJA. | |||
| 4.3.G.ii | The LMS shall support controlled access for authorized users. | |||
| 4.3.G.iii | Access to the LMS shall be managed through authentication and authorization mechanisms defined by OJA. | |||
| 4.3.G.iv | The LMS shall be accessible via a common web browser and must support secure access for authorized external users without requiring connection to the KJB internal network. | |||
| 4.3.H.i | The LMS shall allow configuration of branding elements including logos and visual themes. | |||
| 4.3.H.ii | The LMS shall support configuration of user interface components used to present training content. |
Services (4.4)
| Section | Requirement | Bidder Response | Meets (Y/P/N) | Notes |
| 4.4.A.i | The successful bidder shall identify a project manager who will serve as the primary point of contact throughout implementation. | |||
| 4.4.A.ii | The successful bidder shall participate in a project kickoff meeting with OJA stakeholders to review project objectives, scope, roles, responsibilities, and timelines. | |||
| 4.4.A.iii | The successful bidder shall provide an implementation plan outlining major phases, milestones, and key deliverables. | |||
| 4.4.A.iv | The successful bidder shall coordinate implementation activities with OJA staff and designated project representatives. | |||
| 4.4.A.v | The successful bidder shall participate in regular project status meetings during the implementation period. | |||
| 4.4.B.i | The successful bidder shall configure system settings, roles, permissions, and administrative controls necessary for operation of the LMS. | |||
| 4.4.B.ii | The successful bidder shall support configuration of course catalogs, learning structures, user groupings, and administrative settings. | |||
| 4.4.B.iii | The successful bidder shall support configuration of system branding and visual presentation elements. | |||
| 4.4.B.iv | The successful bidder shall support configuration of authentication and access controls in coordination with OJA. | |||
| 4.4.B.v | The LMS must include a non-production test environment that allows OJA to perform user acceptance testing as well as test configuration changes, course content, and integrations without affecting the production environment. | |||
| 4.4.C.i | The successful bidder shall support the import of user data necessary to establish user accounts and organizational structure within the LMS. | |||
| 4.4.C.ii | The successful bidder shall support import of training records and historical training data where such records are available and provided by OJA in a mutually agreed format. | |||
| 4.4.C.iii | The successful bidder shall provide data import specifications and guidance regarding required file formats and data structures. | |||
| 4.4.C.iv | The successful bidder shall support validation of imported data and system configuration prior to system launch. | |||
| 4.4.D.i | The successful bidder shall provide administrator training covering system configuration, user management, course administration, reporting, and routine system administration. | |||
| 4.4.D.ii | The successful bidder shall provide end-user orientation materials and at least three end-user orientation sessions during implementation and in connection with go-live to demonstrate how users access assigned training, browse available training, complete courses, submit required documentation, and view training records. | |||
| 4.4.D.iii | The successful bidder shall provide onboarding materials for end users that may be used on demand after go-live to support new users, including users added after system launch. | |||
| 4.4.D.iv | End-user orientation and onboarding materials shall be available within the LMS or through vendor-provided documentation so users may access them on demand. | |||
| 4.4.D.v | The successful bidder shall provide training materials or documentation supporting ongoing use and administration of the system. | |||
| 4.4.E.i | Documentation shall include system administration guidance, user documentation, and configuration references. | |||
| 4.4.E.ii | Documentation shall be provided in electronic format and made available to authorized OJA personnel. | |||
| 4.4.F.i | Support availability during standard business hours from Monday through Friday, 7:00 a.m. to 6:00 p.m. Central Time, excluding Kansas Judicial Branch holidays. Bidders must identify any additional support hours available beyond this minimum. Application uptime during these business hours is 99.999% per industry standard for enterprise applications. | |||
| 4.4.F.ii | A ticketing or customer support portal. | |||
| 4.4.F.iii | Documented issue escalation procedures. | |||
| 4.4.F.iv | Defined response and resolution service levels, including minimum response time expectations for critical, high priority, and standard issues. At a minimum: Critical issues: response within 2 hours; High priority issues: response within 4 business hours; Standard issues: response within 1 business day. | |||
| 4.4.F.v | Support for scheduled maintenance and system updates, including notice of planned maintenance at least five (5) business days in advance and description of the frequency of system updates. |
Functional (4.5)
| Section | Requirement | Delivery Method | Bidder Comments |
| 4.5.A.i | Ability to create and manage training courses within the LMS. | ||
| 4.5.A.ii | Ability to provide a searchable course catalog. | ||
| 4.5.A.iii | Ability to assign courses to users, roles, organizational units, or other OJA-defined user groups. | ||
| 4.5.A.iv | Ability for users to self-enroll in available training. | ||
| 4.5.A.v | Ability to maintain a training transcript or training history for each user. | ||
| 4.5.A.vi | Ability to deliver training content in multiple formats (documents, video, modules, assessments). | ||
| 4.5.A.vii | Ability to organize courses into categories or learning paths. | ||
| 4.5.A.viii | Ability to configure course availability dates or enrollment windows. | ||
| 4.5.A.ix | Ability to send automated notifications or reminders for assigned training. | ||
| 4.5.B.i | Ability for authorized administrators to create and manage courses. | ||
| 4.5.B.ii | Ability to upload course materials and training resources. | ||
| 4.5.B.iii | Ability to modify or retire courses without vendor intervention. | ||
| 4.5.B.iv | Ability to configure course completion requirements. | ||
| 4.5.B.v | Ability to assign courses to users, roles, organizational units, or other OJA-defined user groups. | ||
| 4.5.B.vi | Ability to configure course expiration or renewal requirements. | ||
| 4.5.B.vii | Ability to duplicate or clone courses for reuse. | ||
| 4.5.B.viii | Ability to configure course evaluations or feedback forms, including reminders for users to complete assigned or required evaluations. | ||
| 4.5.C.i | Ability to create instructor-led training events. | ||
| 4.5.C.ii | Ability to manage event schedules, physical locations, virtual meeting information, and capacity limits, as applicable. | ||
| 4.5.C.iii | Ability to register users for instructor-led training events. | ||
| 4.5.C.iv | Ability to track attendance for instructor-led training. | ||
| 4.5.C.v | Ability to record completion of instructor-led training events. | ||
| 4.5.C.vi | Ability to associate instructor-led training with learner transcripts. | ||
| 4.5.C.vii | Ability to distribute materials related to instructor-led training. | ||
| 4.5.C.viii | Ability to collect participant feedback or evaluations for instructor-led events, including reminders for users to complete assigned or required evaluations. | ||
| 4.5.D.i | Ability to generate reports on training completion. | ||
| 4.5.D.ii | Ability to generate reports by users, roles, organizational units, or other OJA-defined user groups. | ||
| 4.5.D.iii | Ability to export reports to common formats such as Excel, CSV, or PDF. | ||
| 4.5.D.iv | Ability to provide dashboards displaying training status or progress. | ||
| 4.5.D.v | Ability to identify overdue or incomplete training assignments. | ||
| 4.5.D.vi | Ability to track completion of compliance-based training. | ||
| 4.5.D.vii | Ability to maintain audit records related to training activity. | ||
| 4.5.E.i | Ability to record training completed outside the LMS. | ||
| 4.5.E.ii | Ability for administrators to manually enter external training completion. | ||
| 4.5.E.iii | Ability to associate external training records with user transcripts. | ||
| 4.5.E.iv | Ability to import external training records using standard system functionality. | ||
| 4.5.E.v | Ability for users to submit external training records, including supporting documentation, for administrative review and approval. | ||
| 4.5.F.i | Ability to assign users to roles within the LMS. | ||
| 4.5.F.ii | Ability to organize users by department, unit, or organizational structure. | ||
| 4.5.F.iii | Ability to control access to content based on role or permissions. | ||
| 4.5.F.iv | Ability to deactivate or archive user accounts while retaining training history. | ||
| 4.5.F.v | Ability to manage user accounts and permissions through administrative controls. | ||
| 4.5.G.i | Ability for users to view assigned training upon login. | ||
| 4.5.G.ii | Ability for users to view previously completed training and training records. | ||
| 4.5.G.iii | Ability to search the training catalog. | ||
| 4.5.G.iv | Ability for users to resume partially completed training. | ||
| 4.5.G.v | Ability to access the LMS using modern web browsers. | ||
| 4.5.H.i | Ability to integrate external learning content providers. | ||
| 4.5.H.ii | Ability to provide access to third-party course libraries through the LMS. | ||
| 4.5.H.iii | Ability to manage access to external learning content within the LMS. | ||
| 4.5.H.iv | Ability to import and launch SCORM (Shareable Content Object Reference Model) compliant training modules within the LMS. | ||
| 4.5.H.v | Ability to track learner activity within SCORM modules, including learner progress, assessment results, and time spent. | ||
| 4.5.H.vi | Ability for administrators to upload and manage SCORM training packages using standard LMS administrative tools. | ||
| 4.5.I.i | Vendor provides administrator training covering system configuration and management. | ||
| 4.5.I.ii | Vendor provides end-user orientation materials and at least three end-user orientation sessions during implementation and in connection with go-live. | ||
| 4.5.I.iii | Vendor provides onboarding training materials that may be used on demand for new users after implementation. | ||
| 4.5.I.iv | Vendor provides documentation supporting ongoing system administration. | ||
| 4.5.I.v | Vendor provides documentation supporting end-user access and system use. |
Technical (4.6)
| Section | Requirement | Meets (Y/N) | Bidder Comments |
| 4.6.A.i | The LMS must support Single Sign-On (“SSO”) integration with Microsoft Entra ID for internal KJB users. | ||
| 4.6.A.ii | The LMS must support multi-factor authentication (“MFA”) mechanisms defined or approved by OJA for internal KJB users, including integration with Duo Security where applicable. | ||
| 4.6.A.iii | The LMS must support secure authentication mechanisms for external users who are not part of the OJA identity environment, which must include multi-factor authentication, integration with an external identity provider, or identity verification service. | ||
| 4.6.A.iv | The LMS must support multiple authentication methods to accommodate different user populations while maintaining secure access controls. | ||
| 4.6.B.i | The LMS must support administrative management of user access, including the ability to provision, suspend, deactivate, and manage accounts and permissions for users. | ||
| 4.6.B.ii | The LMS must support role-based access control for administrators and users. | ||
| 4.6.B.iii | The LMS must allow administrators to configure and manage user permissions and access levels. | ||
| 4.6.B.iv | The system must support automatic session timeout after a defined period of user inactivity. | ||
| 4.6.B.v | The LMS should support configuration of the session timeout period to align with OJA security standards. | ||
| 4.6.B.vi | Users must have the ability to manually log out of the system. | ||
| 4.6.C.i | The LMS must maintain audit logs capturing authentication events and administrative actions. | ||
| 4.6.C.ii | Logs must record user identifier, source IP address, timestamp, and action performed. | ||
| 4.6.C.iii | The system must support exporting or forwarding logs to external monitoring or security systems. | ||
| 4.6.D.i | The LMS must be provided as a cloud-hosted service managed by the vendor. | ||
| 4.6.D.ii | The vendor must ensure OJA data processing and storage are handled solely within the United States at all times. | ||
| 4.6.D.iii | The vendor must describe system availability and service continuity capabilities. | ||
| 4.6.D.iv | The vendor must provide Recovery Time Objective (“RTO”) and Recovery Point Objective (“RPO”) information. | ||
| 4.6.D.v | The system must maintain logical separation of customer data in multi-tenant environments. | ||
| 4.6.D.vi | The LMS must support scalable storage capacity sufficient to accommodate training content, user records, and associated materials, and must allow for increases in storage without degradation of system performance. | ||
| 4.6.E.i | The LMS must support integration with external systems using standard APIs or integration mechanisms. | ||
| 4.6.E.ii | The LMS must support import of user data and organizational structures from external sources. | ||
| 4.6.E.iii | The LMS must support migration or import of historical training records during implementation. | ||
| 4.6.E.iv | The LMS must support export of training data and reports in common formats such as CSV or Excel. | ||
| 4.6.F.i | The LMS must support SCORM compliant content packages for delivery of externally developed e-learning modules. | ||
| 4.6.F.ii | The LMS must support standard SCORM tracking elements including learner progress, assessment results, and time spent within the module. | ||
| 4.6.G.i | The system must prevent application error messages from exposing sensitive system or user information. | ||
| 4.6.G.ii | The LMS must support HTTPS (TLS 1.2 or higher) for all data transmission over networks, ensuring encryption of data in transit. | ||
| 4.6.G.iii | The LMS must support automatic redirection of HTTP connections to HTTPS (TLS 1.2 or higher). | ||
| 4.6.G.iv | The LMS must support secure API authentication mechanisms (e.g., OAuth 2.0, JWT). | ||
| 4.6.G.v | The LMS must be compatible with modern web browsers, including Microsoft Edge and Google Chrome. | ||
| 4.6.G.vi | The LMS must provide a user interface that functions on mobile devices or responsive web browsers. | ||
| 4.6.G.vii | The vendor must identify any subcontractors or sub processors used to host or support the LMS service. |
Sec. and Compliance Req (4.7)
| Section | Requirement | Bidder Comments |
| 4.7.i | The proposed LMS must comply with the security requirements contained in the OJA Information Security Requirements Attachment, which will be incorporated into the vendor contract resulting from this RFP. | |
| 4.7.ii | The proposed LMS must comply with the accessibility requirements contained in the OJA Accessibility Addendum, which will be incorporated into the vendor contract resulting from this RFP. |
Add. Compliance Req. (4.8)
| Section | Requirement | Bidder Comments |
| 4.8.A.i | The successful bidder shall provide an evergreen LMS product for which standard product updates, security patches, bug fixes, and releases made generally available to customers are provided as part of the vendor’s standard product lifecycle with no additional charge, licensing event, or contract amendment for the entirety of the contract term, including any renewals. | |
| 4.8.A.ii | The evergreen product requirement includes updates or releases that improve functionality, performance, compatibility, user interface, security, or system reliability, provided such updates are part of the vendor’s standard product offering and are not separately licensed or sold as additional modules or services. | |
| 4.8.A.iii | As part of its proposal, the bidder must identify whether it will provide an evergreen LMS. | |
| 4.8.A.iv | The successful bidder shall ensure the LMS complies with all applicable federal, state, local, or other laws, rules, and regulations. | |
| 4.8.A.v | The successful bidder shall be responsible for proactively monitoring changes to applicable laws, rules, and regulations and initiating any necessary updates, upgrades, releases, adaptations, or modifications to the LMS in advance. | |
| 4.8.A.vi | If a change requires an update, upgrade, release, or other modification required by federal, state, or local law, the successful bidder must deliver and implement the required change to OJA no later than 30 days before the effective date of the applicable law, rule, or regulation. | |
| 4.8.A.vii | All legally required LMS changes must be provided at no additional charge, licensing event, or contract amendment for the full contract term, including any renewals. | |
| 4.8.A.viii | Compliance will be deemed complete only after the updated LMS has successfully passed user acceptance testing and production verification. |
File details come from the government source that posted it. Updated .