RFP Document.pdf
PDF 570 KB Posted
- Attached to
- Learning Management System
- Solicitation number
- 26RFP19989
- Issued by
- Harding County, South Dakota
About this file
RFP Summary: State of South Dakota Learning Management System
This is a Request for Proposal (RFP) issued by the South Dakota Bureau of Human Resources and Administration (BHRA) on behalf of all state agencies for the procurement of a comprehensive Learning Management System (LMS). The State seeks a commercial, off-the-shelf LMS software that supports employee training and professional development across state government agencies and citizens requiring state-issued certifications. The solution must include software licensing, training for state personnel, and ongoing maintenance and support through an annual user license agreement. Offerors may propose a solution hosted by the State, hosted by the vendor, or both options as separate proposals. The deadline for written inquiries is November 9, 2026, with responses provided by November 16, 2026. Proposals are due by 11:59 p.m. CST on December 7, 2026, to EOD@state.sd.us with a maximum email size of 20MB. The anticipated award decision is February 2, 2027. The contract term is five years with the opportunity for up to two one-year renewal extensions, which are not automatic. The RFP reference number is 26RFP19989, and the State Point of Contact is Natasha Bothun at Natasha.Bothun@state.sd.us.
The RFP does not specify a total contract value or identify any set-asides. Offerors must provide detailed cost proposals including staffing, travel, and other costs separated by implementation year and ongoing annual costs, with software licenses clearly identified as either perpetual or term-based. The proposal must detail all third-party software licensing costs the State will incur. The State currently operates an existing LMS that services all agencies with division-specific controls; the new system must transfer current and future data from this existing source. The State requires compliance with specific IT standards including federated identity architecture with Single Sign-On integration to Microsoft Entra ID and mySD SSO via OpenID Connect, vulnerability scanning, load balancing capabilities, and data accessibility through Microsoft Power BI, ESRI, and Tableau. The State will conduct web application vulnerability scans for vendor-hosted solutions, and offerors must provide the complete scan report. Offerors must demonstrate the ability to support 10,000+ concurrent state employees and provide detailed security certifications, data loss prevention methodologies, and disaster recovery plans. Background investigations are required for all offeror and subcontractor employees with access to personally identifiable information, FERPA-protected data, protected health information, or federal tax information.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Security and Vendor Questions v3.3 Production.docx | DOCX document | |
| Appendix A.docx | DOCX document |
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
UPDATED OCTOBER 26, 2026 1
STATE OF SOUTH DAKOTA
INFORMATION TECHNOLOGY (IT) RFP
Bureau of Human Resources and Administration 500 East Capitol Avenue
Pierre, SD 57501
Learning Management System
PROPOSALS ARE DUE NO LATER THAN DECEMBER 7, 2026
RFP #: 26RFP19989 STATE POC: Natasha Bothun EMAIL: Natasha.Bothun@state.sd.us
READ CAREFULLY
FIRM NAME: AUTHORIZED SIGNATURE:
ADDRESS: TYPE OR PRINT NAME:
CITY/STATE: TELEPHONE NO:
ZIP (9 DIGITS): FAX NO:
E-MAIL:
PRIMARY CONTACT INFORMATION
CONTACT NAME:
TELEPHONE NO:
FAX NO: E-MAIL:
UPDATED OCTOBER 26, 2026 2
1 General Information
1.1 Purpose of Request for Proposal (RFP)
The purpose of this Request for Proposal is to solicit bids for a learning management system (LMS) that supports the training and professional development of employees across government agencies in the State of South Dakota. The agency working on behalf of all state agencies for this RFP is the South Dakota Bureau of Human Resources and Administration (BHRA). The LMS should be comprised of:
1.1.1 Commercial, off-the-shelf (COTS) LMS software that allows State Of South Dakota personnel to administer and deliver training to employees and state citizens when required by individual agencies in the course of performing their duty to the public.
1.1.2 Training for State Government personnel in the use of the LMS; and
1.1.3 Ongoing software maintenance and support through an annual user license Agreement.
1.1.4 Offerors can propose a solution hosted by the State or alternatively a solution hosted by the Offeror, or both. If the Offeror proposes a solution hosted by the State and a solution hosted by the Offeror, the Offeror should submit TWO (2) separate proposals. Do not combine into one proposal.
1.2 Issuing Office and RFP Reference Number
The BHRA (“Agency”) is the issuing office for this document and all subsequent addenda relating to it, on behalf of the State of South Dakota (“State”). The reference number for this transaction is RFP# 26RFP19989 This reference number must be referred to on all proposals, correspondence, and documentation relating to this RFP. For purposes of this RFP, the State’s centralized IT agency, the Bureau of Information and Technology (“BIT”), must approve all IT related purchases.
1.3 Schedule of Activities (Subject to Change)
All deadlines in the Schedule of Activities are due by 11:59 p.m. CST. The Schedule of Activities for this RFP is as follows:
RFP Publication November 2, 2026 Deadline for Submission of Written Inquiries November 9, 2026 Deadline for Responses to offeror Questions November 16, 2026 Deadline for Proposal Submission December 7, 2026 Evaluation of Proposals to Determine Short List (If required) December 15, 2026 Discussions / Technical Review Dec. 17 – Jan. 11 Demonstrations and presentations (if required) January 19-22, 2027 Proposal Revisions (if required) January 29, 2027 Anticipated Award Decision/Contract Negotiation February 2, 2027
UPDATED OCTOBER 26, 2026 3
1.4 Submitting a Proposal
All proposals must be completed and received by the Agency by the date and time indicated in Section 1.3 Schedule of Activities.
Proposals received after the Deadline for Proposal Submission will be late and ineligible for consideration.
All proposals must be signed, in ink or electronically, by a representative of the offeror who is legally authorized to bind the offeror to the proposal. Proposals that are not properly signed may be rejected. The offeror’s proposal must be prepared pursuant to the requirements of Section 6 Proposal Submission Requirements of this RFP.
The State will only accept electronic proposals via email.
Each offeror must provide an electronic version of the proposal. The electronic version should be provided in MS Word or in PDF format to EOD@state.sd.us. The email, including attachments, must be limited to 20MB in size.
The offeror must provide one (1) copy of the offeror’s entire proposal, including all attachments, in Microsoft Word or in PDF format by email to EOD@state.sd.us.
The online submission must be marked with the appropriate RFP Number and Title Proposals must be addressed and labeled as follows:
REQUEST FOR PROPOSAL # 26RFP19989 PROPOSAL TITLE State of South Dakota Learning Management System PROPOSAL DUE December 7, 2026 STATE POC Natasha Bothun Address: Natasha.bothun@state.sd.us
No proposal will be accepted from, or no contract or purchase order will be awarded to, any person, firm, or corporation that is in arrears upon any obligations to the State of South Dakota, or that otherwise may be deemed irresponsible or unreliable by the State of South Dakota.
1.5 Certification Regarding Debarment, Suspension, Ineligibility, and Voluntary
Exclusion – Lower Tier Covered Transactions
By signing and submitting this proposal, the offeror certifies that neither it nor its principals is presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from participation, by any Federal department or agency, from transactions involving the use of Federal funds. Where the offeror is unable to certify to any of the statements in this certification, the offeror shall attach an explanation to its offer.
UPDATED OCTOBER 26, 2026 4
1.6 Non-Discrimination Statement
The State of South Dakota requires that all contractors, vendors, and suppliers doing business with any State agency, department, or institution, provide a statement of non-discrimination. By signing and submitting their proposal, the offeror certifies they do not discriminate in their employment practices with regard to race, color, creed, religion, age, sex, ancestry, national origin, or disability.
1.7 Restriction of Boycott of Israel
For contractors, vendors, suppliers, or subcontractors with five (5) or more employees who enter into a contract with the State of South Dakota that involves the expenditure of one hundred thousand dollars ($100,000) or more, by submitting a response to this solicitation or agreeing to contract with the State, the bidder or offeror certifies and agrees that the following information is correct:
The bidder or offeror, in preparing its response or offer or in considering proposals submitted from qualified, potential vendors, suppliers, and subcontractors, or in the solicitation, selection, or commercial treatment of any vendor, supplier, or subcontractor, has not refused to transact business activities, has not terminated business activities, and has not taken other similar actions intended to limit its commercial relations, related to the subject matter of the bid or offer, with a person or entity on the basis of Israeli national origin, or residence or incorporation in Israel or its territories, with the specific intent to accomplish a boycott or divestment of Israel in a discriminatory manner. It is understood and agreed that, if this certification is false, such false certification will constitute grounds for the State to reject the bid or response submitted by the bidder or offeror on this project and terminate any contract awarded based on the bid or response. The successful bidder or offeror further agrees to provide immediate written notice to the contracting executive branch agency if during the term of the contract it no longer complies with this certification and agrees such noncompliance may be grounds for contract termination.
1.8 Certification Relating to Prohibited Entity
For contractors, vendors, suppliers, or subcontractors who enter into a contract with the State of South Dakota by submitting a response to this solicitation or agreeing to contract with the State, the bidder or offeror certifies and agrees that the following information is correct:
The bidder or offeror, in preparing its response or offer or in considering proposals submitted from qualified, potential vendors, suppliers, and subcontractors, or in the solicitation, selection, or commercial treatment of any vendor, supplier, or subcontractor, is not a prohibited entity, regardless of its principal place of business, that is ultimately owned or controlled, directly or indirectly, by a foreign national, a foreign parent entity, or foreign government from China, Iran, North Korea, Russia, Cuba, or Venezuela, as defined by South Dakota Codified Law § 5-18A. It is understood and agreed that, if this certification is false, such false certification will constitute grounds for the State to reject the bid or response submitted by the bidder or offeror on this project and terminate any contract awarded based on the bid or response. The successful bidder or offeror further agrees to provide immediate written notice to the contracting executive branch agency if during the term of the contract it no longer complies with this certification and agrees such noncompliance may be grounds for contract termination and would be cause to suspend
UPDATED OCTOBER 26, 2026 5
and debar a business under SDCL § 5-18D-12.
1.9 Modification or Withdrawal of Proposals
Proposals may be modified or withdrawn by the offeror prior to the established due date and time.
No oral, telephonic, telegraphic or facsimile responses or modifications to informal, formal bids, or Request for Proposals will be considered.
1.10 Questions Regarding RFP
All written questions should be sent to: SD RFP Project EOD@state.sd.us, only emailed questions will be accepted.
Each offeror may submit questions via email concerning this RFP to obtain clarification of requirements. No questions will be accepted after the date and time indicated in the above schedule of activities. Email questions to the email address listed above with the subject line “RFP# 26RFP19989 ”. The questions and their answers will be sent to all offerors that submitted Letters of Intent, submitted questions, or requested the questions and answers via email before the proposal submittal date and will be sent by the date and time indicated in the above calendar of events. Offeror may not rely on any other statements, either of a written or oral nature, that alter any specification or other term or condition of this RFP that have not originated from the SD RFP Project Contact. Offerors will be notified in the same manner as indicated above regarding any modifications to this RFP. Offerors and their agents may not contact any state employee other than the buyer of record regarding any of these matters during the solicitation and evaluation process.
Inappropriate contacts are grounds for suspension and exclusion from specific procurements.
1.11 Prohibition on Solely AI-Generated Submissions
All questions and proposals (“Submissions”) submitted in response to this RFP must be thoroughly vetted, verified, and validated by the offeror’s human staff. Submissions the State believes are solely generated by Artificial Intelligence (AI) without substantive human review and oversight are strictly prohibited and may result in the disqualification of the proposal or rejection of the submitted questions.
1.12 Proprietary Information
The proposal of the successful offeror(s) becomes public information. Proprietary information can be protected under limited circumstances such as client lists and non-public financial statements. An entire proposal may not be marked as proprietary.
Offerors must clearly identify in the Executive Summary and mark in the body of the proposal any specific proprietary information they are requesting to be protected. The Executive Summary must contain specific justification explaining why the information is to be protected. Proposals may be reviewed and evaluated by any person at the discretion of the State. All materials submitted become the property of the State of South Dakota and may be returned only at the State's option.
mailto:EOD@state.sd.us
UPDATED OCTOBER 26, 2026 6
1.13 Length of Contract
The length of the contract will be for a term of five year(s). The State will have the opportunity to renew the contract annually for up to two one-year time extensions. The extension(s) will not be automatic.
1.14 Governing Law
This RFP will be governed by and construed in accordance with the laws of the State of South Dakota. Any lawsuit pertaining to or affecting this RFP will be venued in Circuit Court, Sixth Judicial Circuit, Hughes County, South Dakota.
1.15 Site Visit
If site visits are required, they will be scheduled before the submission of the proposal.
Site visits will be made at the offeror’s expense.
1.16 Presentations/Demonstrations
At the State’s discretion, the State may require a presentation or demonstration by an offeror to clarify a proposal. However, the State may award a contract based on the initial proposals received without a presentation or demonstration by the offeror. If presentations or demonstrations are required, they will be scheduled after the submission of proposals. Presentations and demonstrations will be made at the offeror’s expense.
1.17 Discussions
At the State’s discretion, the offeror may or may not be invited to have discussions with the State. The discussions can be before or after the RFP has been submitted.
Discussions will be made at the offeror’s expense.
1.18 Technical Review
At the State’s discretion, the State may require a technical review of the offeror based on the offeror’s proposal and response to the Security and Vendor Questionnaire.
1.19 Negotiations
This process is a Request for Proposal/Competitive Negotiation process. Each proposal will be evaluated, and each respondent will be available for negotiation meetings at the State’s request. The State reserves the right to negotiate on any component of every proposal submitted. From the time the proposals are submitted until the formal award of a contract, each proposal is considered a working document and as such, will be kept confidential. The negotiation discussions will also be held as confidential until such time as the award is completed.
UPDATED OCTOBER 26, 2026 7
2 Standard Contract Terms and Conditions
Any contract or agreement resulting from this RFP will include the State’s standard terms and conditions as listed below, the State’s standard Information Technology (“IT”) contract terms listed in Appendix A, and any additional terms and conditions as negotiated by the parties. The offeror must indicate in its response any issues it has with specific contract terms. If the offeror does not indicate that there is an issue with a specific contract term, then the offeror will be deemed to have accepted the contract terms as written.
2.1 The Contractor will perform those services described in the Scope of Work, attached hereto as Section 3 of the RFP and by this reference incorporated herein.
2.2 The Contractor’s services under this Agreement will start on _______, and end on
________, unless terminated sooner pursuant to the terms of the Agreement.
2.3 The Contractor will not use State equipment, supplies, or facilities. The Contractor will provide the State with its Employer Identification Number, Federal Tax Identification Number, or Social Security Number upon execution of this Agreement.
2.4 The State will make payment for services upon satisfactory completion of the services.
The TOTAL CONTRACT AMOUNT is an amount not to exceed $ . The State will not pay Contractor's expenses as a separate item. Payment will be made pursuant to itemized invoices submitted with a signed state voucher. Payment will be made consistent with SDCL chapter 5-26.
2.5 The Contractor agrees to indemnify the State of South Dakota, its officers, agents, and employees, from and against all claims or proceedings for actions, suits, damages, liabilities, other losses or equitable relief that may arise at least in part as a result of an act or omission in performing services under this Agreement. The Contractor will defend the State of South Dakota, its officers, agents, and employees against any claim, including any claim, action, suit, or other proceeding related to the claim. The Contractor’s obligation to indemnify includes the payment of attorney fees and other costs of defense.
In defending the State of South Dakota, its officers, agents, and employees, the Contractor will engage other professionals, subject to the written approval of the State which will not be unreasonably withheld. Notwithstanding the foregoing, the State may, in its sole discretion and at the expense of the Contractor, engage attorneys and other professionals to defend the State of South Dakota, its officers, agents, and employees, or to assist the Contractor in the defense. This section does not require the Contractor to be responsible for or defend against claims or proceedings for damages, liabilities, losses, or equitable relief arising solely from errors or omissions of the State, its officers, agents, or employees.
2.6 During the term of this Agreement, the Contractor will obtain and maintain in force insurance coverage of the types and with the limits as follows:
2.6.1 Commercial General Liability Insurance:
The Contractor will maintain occurrence based commercial general liability insurance or equivalent form with a limit of not less than $1 million for each occurrence. If such insurance contains a general aggregate limit it will apply separately to this Agreement or be no less than two times the occurrence limit.
The insurance policy will name the State of South Dakota, its officers and
UPDATED OCTOBER 26, 2026 8
employees, as additional insureds, but liability coverage is limited to claims not barred by sovereign immunity. The State of South Dakota, its officers and employees do not hereby waive sovereign immunity for discretionary conduct as provided by law.
2.6.2 Professional Liability Insurance or Miscellaneous Professional Liability Insurance:
The Contractor will procure and maintain professional liability insurance or miscellaneous professional liability insurance with a limit not less than $1 million.
2.6.3 Business Automobile Liability Insurance:
The Contractor will maintain business automobile liability insurance or equivalent form with a limit of not less than $1 million for each accident. Such insurance will include coverage for owned, hired, and non-owned vehicles.
2.6.4 Workers’ Compensation Insurance:
The Contractor will procure and maintain workers’ compensation and employers’ liability insurance as required by South Dakota or federal law.
Before beginning work under this Agreement, Contractor will furnish the State with properly executed Certificates of Insurance which will clearly evidence all insurance required in this Agreement. In the event a substantial change in insurance, issuance of a new policy, cancellation, or nonrenewal of the policy, the Contractor agrees to provide immediate notice to the State and provide a new certificate of insurance showing continuous coverage in the amounts required. Contractor will furnish copies of insurance policies if requested by the State.
2.7 While performing services under this Agreement, the Contractor is an independent contractor and not an officer, agent, or employee of the State of South Dakota.
2.8 The Contractor agrees to report to the State any event encountered in the course of performance of this Agreement which results in injury to the person or property of third parties, or which may otherwise subject Contractor or the State to liability. The Contractor will report any such event to the State immediately upon discovery.
The Contractor's obligation under this section will only be to report the occurrence of any event to the State and to make any other report provided for by their duties or applicable law. The Contractor’s obligation to report will not require disclosure of any information subject to privilege or confidentiality under law (e.g., attorney-client communications).
Reporting to the State under this section will not excuse or satisfy any obligation of the Contractor to report any event to law enforcement or other entities under the requirements of any applicable law.
2.9 This Agreement may be terminated by either party hereto upon thirty (30) days’ written notice. In the event the Contractor breaches any of the terms or conditions of this Agreement, this Agreement may be terminated by the State at any time with or without notice. If termination for a breach is affected by the State, any payments due to the Contractor at the time of termination may be adjusted to cover any additional costs to the State because of the Contractor's breach. Upon termination the State may take over the work and may award another party an agreement to complete the work under this Agreement. If after the State terminates for a breach by the Contractor it is determined that the Contractor was not at fault, then the Contractor will be paid for eligible services
UPDATED OCTOBER 26, 2026 9
rendered and expenses incurred up to the date of termination.
2.10 This Agreement depends upon the continued availability of appropriated funds and expenditure authority from the Legislature for this purpose. If for any reason the Legislature fails to appropriate funds or grant expenditure authority, or funds become unavailable by operation of law or federal funds reductions, this Agreement will be terminated by the State upon five (5) business days’ written notice. The Contractor agrees that termination for any of these reasons is not a default by the State nor does it give rise to a claim against the State or any officer, agent, or employee of the State, and the Contractor waives any claim against the same.
2.11 This Agreement may not be assigned without the express prior written consent of the
State. This Agreement may not be amended except in writing, which writing will be expressly identified as a part of this Agreement and be signed by an authorized representative of each of the parties to this Agreement.
2.12 This Agreement will be governed by and construed in accordance with the laws of the
State of South Dakota, without regard to any conflicts of law principles, decisional law, or statutory provision which would require or permit the application of another jurisdiction’s substantive law. Venue for any lawsuit pertaining to or affecting this Agreement will be in Circuit Court, Sixth Judicial Circuit, Hughes County, South Dakota.
2.13 The Contractor will comply with all federal, tribal, state, and local laws, regulations, ordinances, guidelines, permits, requirements, and other standards applicable to providing services pursuant to this Agreement and will be solely responsible for obtaining current information on such requirements. Nothing herein will constitute a waiver by the State to any defense to jurisdiction nor will anything under this Agreement constitute an acknowledgement by the State that any tribe has or exercises any jurisdiction over this Agreement or the parties.
2.14 The Contractor may not use subcontractors to perform the services described in this
Agreement without the express prior written consent of the State. The Contractor will include provisions in its subcontracts requiring its subcontractors to comply with the applicable provisions of this Agreement, to indemnify the State, and to provide insurance coverage for the benefit of the State in a manner consistent with this Agreement. The Contractor will cause its subcontractors, agents, and employees to comply with applicable federal, tribal, state, and local laws, regulations, ordinances, guidelines, permits, and other standards and will adopt such review and inspection procedures as are necessary to assure such compliance. The State, at its option, may require the vetting of any subcontractors. The Contractor will assist in the vetting process.
2.15 The State reserves the right to reject any person from performing services under this
Agreement who the State believes would be detrimental to the services, presents insufficient skills, presents inappropriate behavior, or is considered by the State to be a security risk.
2.16 The Contractor hereby acknowledges and agrees that all reports, plans, specifications, technical data, miscellaneous drawings, software system programs and documentation, procedures, or files, operating instructions and procedures, source code(s) and documentation, including those necessary to upgrade and maintain the software program, and all information contained therein provided to the State by the Contractor in
UPDATED OCTOBER 26, 2026 10
connection with its performance of services under this Agreement will belong to and is the property of the State and will not be used in any way by the Contractor without the written consent of the State. Papers, reports, forms, software programs, source code(s), and other material which are a part of the work under this Agreement will not be copyrighted without written approval of the State.
2.17 The Contractor certifies that neither Contractor nor its principals are presently debarred, suspended, proposed for debarment or suspension, or declared ineligible from participating in transactions by the federal government or any state or local government department or agency. Contractor further agrees that it will immediately notify the State if during the term of this Agreement Contractor or its principals become subject to debarment, suspension, or ineligibility from participating in transactions by the federal government, or by any state or local government department or agency.
2.18 By signing this Agreement, the Contractor certifies and agrees that is has not refused to transact business activities, have not terminated business activities, and have not taken other similar actions intended to limit its commercial relations, related to the subject matter of this Agreement, with a person or entity that is either the State of Israel, or a company doing business in or with Israel or authorized by, licensed by, or organized under the laws of the State of Israel to do business, or doing business in the State of Israel, with the specific intent to accomplish a boycott or divestment of Israel in a discriminatory manner. It is understood and agreed that, if this certification is false, such false certification will constitute grounds for the State to terminate this Agreement. During the term of this Agreement, if the Contractor no longer complies with this certification, the Contractor agrees to provide immediate written notice to the State and agrees such noncompliance may be grounds for termination of this Agreement.
2.19 Pursuant to South Dakota Codified Law § 5-18A, by entering into this Agreement with the
State of South Dakota, the Contractor certifies and warrants that the Contractor is not a prohibited entity, regardless of its principal place of business, that is ultimately owned or controlled, directly or indirectly, by a foreign national, a foreign parent entity, or foreign government from China, Iran, North Korea, Russia, Cuba, or Venezuela, as defined by South Dakota Codified Law § 5-18A.
The Contractor agrees that if this certification is false, the State may terminate this Agreement with no further liability to the State. The Contractor further agrees to provide immediate written notice to the State if during the term of the contract it no longer complies with this certification, and the Contractor agrees such noncompliance may be grounds for contract termination and would be cause to suspend and debar a business under SDCL § 5-18D-12.
2.20 The Contractor (i) understands neither a state legislator nor a business in which a state legislator has an ownership interest may be directly or indirectly interested in any contract with the State that was authorized by any law passed during the term for which that legislator was elected, or within one year thereafter, and (ii) has read South Dakota Constitution Article 3, Section 12 and has had the opportunity to seek independent legal advice on the applicability of that provision to this Agreement. By signing this Agreement, the Contractor certifies that this Agreement is not made in violation of the South Dakota Constitution Article 3, Section 12.
UPDATED OCTOBER 26, 2026 11
2.21 Any notice or other communication required under this Agreement will be in writing and sent to the address set forth above. Notices will be given by and to Natasha Bothun on behalf of the State, and by and to , on behalf of the Contractor, or such authorized designees as either party may from time to time designate in writing. Notices or communications to or between the parties will be deemed to have been delivered when mailed by first class mail, provided that notice of default or termination will be sent by registered or certified mail, or, if personally delivered, when received by such party.
2.22 In the event that any court of competent jurisdiction will hold any provision of this
Agreement unenforceable or invalid, such holding will not invalidate or render unenforceable any other provision of this Agreement.
2.23 All other prior discussions, communications, and representations concerning the subject matter of this Agreement are superseded by the terms of this Agreement, and except as specifically provided in this Agreement, this Agreement constitutes the entire agreement with respect to the subject matter.
2.24 The waiver by either party of a breach or violation of any provisions of this Agreement will not operate as, or be construed to be, a waiver of any subsequent breach of the same or other provision of this Agreement.
2.25 Nothing in this Agreement is intended to constitute a waiver of sovereign immunity by or on behalf of the State of South Dakota, its agencies, officers, or employees.
2.26 Neither party will disclose the contents of the Agreement except as required by applicable law or as necessary to carry out the terms of the Agreement or to enforce that party’s rights under this Agreement. The Contractor acknowledges that the State of South Dakota and its agencies are public entities and thus are bound by South Dakota open meetings and open records laws. It is therefore not a breach of this Agreement for the State to take any action that the State reasonably believes is necessary to comply with the South Dakota open records or open meetings laws, including, without limitation, posting this Agreement on the website pursuant to SDCL § 1-27-46.
3 Scope of Work
(General Capabilities)
3.1 The South Dakota BHRA is seeking an online learning management system that supports employee training and professional development needs across all state agencies and the citizens of South Dakota where state-issued certifications are required. Currently, there is an LMS in place that does service all agencies through an overall LMS with each agency having control of their own LMS through the system. The LMS must provide a software interface that can transfer current and future data from existing LMS source.
3.2 The ideal LMS will support and provide up-to-date training courses for each agency’s specific professional disciplines, as well as general overall skill building and competency development training for state employees at all levels. The system will be centralized with individual agency systems contained within it. The LMS will have access to a library of pre-developed content that is regularly updated. It will also be able to store any content purchased or created by the State of South Dakota.
UPDATED OCTOBER 26, 2026 12
3.3 The LMS will need to have registration capabilities for virtual, on-demand, and in-person learning, as well as the capability to issue billing directly from the system.
3.4 The system should include the following capabilities:
3.4.1 Availability and User Capacity:
• 24/7 accessibility through a variety of devices including computers, smartphones, and tablets.
• Ability to support users as assigned by BHRA or individual agencies including external (non-state) individuals.
• Ability to accommodate live, interactive, visual trainings as well as self-guided training modules.
• Ability to allow many concurrent users within the system. Please identify system capacity and limitations.
3.4.2 Content:
• Access to specific agency-related content, and the ability to store purchased and curated content.
• Access to professional/leadership development content.
• Training modules containing the most recent evidence-based processes (five years old or less) and automatically updated with the newest researched training modules for an abundance of areas, including compliance and cyber security content.
• Ability to customize and upload department-specific training information/modules, articles, and policies.
• Ability to upload recorded live training for viewing.
• Access to a variety of learning methodologies including gamification, video and text, demonstration, quizzes as needed, etc.
• Generation of a checklist for competencies and hands-on demonstration as well as support for pre and post-tests as appropriate.
• Storage capabilities for all content.
• Ability to transfer stored data from any existing LMS to the new LMS.
3.4.3 Monitoring and Report Capabilities:
• Ability to set deadlines for specific training courses for identified groups.
• Ability to track registration, completion, and delinquency for each training.
• Ability to generate notifications and reminders to employees and supervisors for upcoming training deadlines or delinquencies.
• Ability to generate continuing education credit forms and training completion certificates.
• Ability to generate applicable pre-tests, any applicable pre-course work, and reminders prior to training.
• Support for pre- and post-test options with analysis and data reports.
• Coordination with current HRIS for data sharing related to employee information, licensure, and other trainings completed.
• Support for an administrator dashboard to allow customization for each agency.
3.4.4 Accessibility:
• Access for 10,000+ state employees.
• Implement a federated identity architecture that segregates authentication by user persona, either by separate login pages or by dynamically routing public citizens to mySD Single Sign On (SSO) via OpenID Connect (OIDC) and state employees and contractors to the State-managed Microsoft Entra ID Tenant.
UPDATED OCTOBER 26, 2026 13
All authentication must be delegated to these authoritative Identity Providers (IdPs); the local system is strictly prohibited from storing user passwords.
• Overall system with individual access for individual agencies’ LMS within the central LMS.
• Access for citizens for agencies that require state certifications.
3.4.5 Additional Capabilities/Support:
• Registration capabilities for virtual, in-person and content learning.
• Ability for employees to stop a training module and start back up where they left off at a later date.
• Ability to provide on-site training for learning management system and ongoing training as needed.
• Ability to bill agencies and outside entities for original content trainings. The billing will need to be able to feed into our accounting system.
• Ability to group employees together using a user-defined code.
• Ability for admin to manually create and configure groups based on variety of criteria.
• Ability to use multiple codes for employees.
• Development of curriculums for employees or employee groups.
• Assignment of training curriculums to employees.
• Ability for admin to create dynamic learning assignments with options for one-time use and recurring.
• Ability for end users to log training completed outside of the LMS.
• Ability for admin to create default and custom email based on learning object and assignment.
• Ability for admin to load video files via upload or embed.
• Ability for admin to easily configure welcome/landing page.
• Ability to conduct pulse surveys for all employees.
• The Offeror must describe how the system can adapt to business necessary interfaces using widely adopted open APIs and standards. Additionally, the South Dakota BHRA expects that the Offeror will make available/expose software services and publish documentation for those software services that would enable third party developers to interface other business applications. A detailed description of system capability shall be included in the proposal.
• The State will own the data tables and will be able to manipulate data, run reports as needed, pull code tables, access raw data and develop dashboards as needed through Microsoft Power BI, ESRI, Tableau, and associated platforms.
3.5 LMS General Requirements
LMS General Requirements Offeror Response Offeror Explanation System—General: The LMS must be able to:
1. Comply with South Dakota Bureau of Information and Technology (BIT) technical standards.
http://bit.sd.gov/standards/
Yes☐ No☐ NA☐
2. Run on Windows 10 desktop or later version (if the LMS requires a client).
Yes☐ No☐ NA☐ http://bit.sd.gov/standards/
UPDATED OCTOBER 26, 2026 14
3. Serve as a centralized system with up to 10,000 system users simultaneously, including users at remote locations with low bandwidth.
Yes☐ No☐ NA☐
4. Ability for division-specific LMS systems within the centralized system.
Yes☐ No☐ NA☐
5. Be accessed using the latest version of the most used browser on any operating system (Microsoft Edge, Mozilla Firefox, Safari, Chrome).
Yes☐ No☐ NA☐
6. Be available as (check all that apply):
a. Software as a service/cloud-hosted program
b. Software the State can maintain on its own servers.
If you offer more than one solution,
7. Content must be available and accessible on smartphones, iPads, and other mobile devices (please identify the brands and models of mobile devices, operating systems, and Internet browsers that are compatible with your LMS).
Yes☐ No☐ NA☐
8. Meet SCORM, AICC and Tin Can API standards.
Yes☐ No☐ NA☐
9. Will not require an inordinate amount of a full-time State IT professional’s time to administer and resolve technical problems (If BHRA decides to purchase an LMS that is hosted by the Offeror)
Yes☐ No☐ NA☐
10. Offer defined annual maintenance costs.
Yes☐ No☐ NA☐
11. Store, broadcast, and track courses produced in widely varying digital formats, especially digitized video, and courses with multiple digital files in differing formats.
Yes☐ No☐ NA☐
12. Combine or associate different digital files into a single training resource.
Yes☐ No☐ NA☐
13. Conduct pulse surveys from the LMS. Yes☐ No☐ NA☐
14. Organize courses into a catalog searchable by subject, keywords, title, and instructor names.
UPDATED OCTOBER 26, 2026 15
15. Include a pre-developed catalog of courses for employees to take.
Including but not limited to
a. Compliance Training
b. Cyber Security Training
16. Archive training-related documents. Yes☐ No☐ NA☐ 17 Operate internally with other COTS
LMSs and third-party training systems.
Yes☐ No☐ NA☐
18. Import historical and future employee data from BHRA’s HRIS, including name, position, location, employee number, and supervisor in a manner that prevents unauthorized access to, or disclosure of, personally identifiable information (PII).
Yes☐ No☐ NA☐
19. Integrate other legacy data sets in a manner that prevents unauthorized access to, or disclosure of, personally identifiable information.
Yes☐ No☐ NA☐
20. Alter training requirements to account for a position change, as when an employee changes jobs.
Yes☐ No☐ NA☐
21. Track certifications, continuing education units (CEUs), and licenses within employee training profiles.
Yes☐ No☐ NA☐
22. Automatically update training profiles with course completion and attendance information, test scores, certification dates, license information, CEUs earned, and other training information.
Yes☐ No☐ NA☐
23. Provide a wide variety of predefined reports.
Yes☐ No☐ NA☐
24. Generate reports by individual, group, course, and time period.
Yes☐ No☐ NA☐
25. Easily create custom reports with LMS data in multiple formats, including Microsoft Excel, and provide reports on direct costs, such as equipment, instructors, and locations
Yes☐ No☐ NA☐
26. Provide access to different reports and data based on permission level.
Yes☐ No☐ NA☐
27. Output data in Excel and other programs.
Yes☐ No☐ NA☐
28. Allow specified users to manually override certain LMS features.
Yes☐ No☐ NA☐
29. Generate an easy-to-print course calendar that automatically updates when a course is added.
UPDATED OCTOBER 26, 2026 16
30. Update the user’s Microsoft Outlook calendar when the user enrolls in a class, and when enrollment is confirmed or canceled.
Yes☐ No☐ NA☐
31. Assign training by job title, manager/supervisor, and work location.
Yes☐ No☐ NA☐
32. Track certifications of varying lengths. Yes☐ No☐ NA☐
33. Reset certification periods for employees after course completion.
Yes☐ No☐ NA☐
34. Allow outside contractors to register for courses or take exams.
Yes☐ No☐ NA☐
35. Alert users of any prerequisites for courses, training, or tests.
Yes☐ No☐ NA☐
36. Provide monitoring data of an online course (Example: Did the user only view half an e-learning course? If two questions in a test were answered incorrectly, what were those two questions?)
Yes☐ No☐ NA☐
37. Create a waiting list once a class is full. Yes☐ No☐ NA☐
38. Register a user for a course that the user has taken before.
Yes☐ No☐ NA☐
39. Create and compile class surveys. Yes☐ No☐ NA☐
40. Produce and easily print course completion certificates and rate quality of courses
Yes☐ No☐ NA☐
41. Allow an administrator to cancel or reschedule a class or class section.
3.5.1 General Requirements for Employee Users
The Bureau of Human Resources and Administration wants the LMS to be easy to use and to require little or no training to perform basic functions, such as enrolling for a course or authorized viewing of an employee training profile.
Employees and other LMS Users will:
42. Easily navigate the LMS and perform basic tasks, such as class enrollment,
(a) after one hour of classroom training,
(b) a one-hour online tutorial or (c) reading instructions from a manual the employee can view on a computer screen or mobile device.
Yes☐ No☐ NA☐
43. View and print employee training plans, complete courses, plan progress, test scores, certifications, CEUs, and licenses.
UPDATED OCTOBER 26, 2026 17
44. Click on a help button that leads to searchable user manual-type information, including a table of contents.
Yes☐ No☐ NA☐
45. Receive automatic confirmations of class enrollments, changes, cancellations, and completions.
Yes☐ No☐ NA☐
46. Receive an automatic email reminder close to the start of the course.
Yes☐ No☐ NA☐
47. Receive an automatic alert email before a certification expires.
Yes☐ No☐ NA☐
48. Submit an evaluation or other feedback after completing a
3.5.2 General Requirements for Supervisors and Managers
To have a unified State Government-wide training system for all agencies to use for all development and training needs. The system will allow for easy administration of trainings and generate detailed reports on the status of required trainings for employees. The BHRA wants to make it easy for supervisors and managers to plan, monitor, and assess training among their employees, whether or not the training was obtained in-house, or through a third party.
Senior managers want to easily determine if strategic planning goals, specifically those involving training are progressing or have been met. They also want to track and analyze training costs, including the amount of time employees spend in training.
Supervisors and Managers will:
49. See complete employee training profiles and track the training progress of an individual employee or group of employees.
Yes☐ No☐ NA☐
50. Be able to customize an employee’s training plan.
Yes☐ No☐ NA☐
51. Generate a report showing a unit’s or the entire division's progress toward strategic plan training goals.
Yes☐ No☐ NA☐
52. Generate a report showing gaps in an employee’s or employee group’s training plans.
Yes☐ No☐ NA☐
53. Generate a calendar showing scheduled training for a group of employees for a week, month, year, or years.
Yes☐ No☐ NA☐
54. Receive automatic email notices when employees receive required training notices
Yes☐ No☐ NA☐
55. Receive automatic email notices when employees have completed courses.
Yes☐ No☐ NA☐
56. Receive an automatic email before an employee’s certification expires.
UPDATED OCTOBER 26, 2026 18
57. Pre-authorize an employee’s enrollment in certain courses and automatically receive an email when an employee tries to enroll for a course that is not pre-authorized.
Yes☐ No☐ NA☐
58. Enroll employees individually or by group and automatically send emails notifying them of enrollment.
4 Project Deliverables/Approach/Methodology
The offeror must describe in detail how its proposed deliverables will meet the needs of the State as described in Section 3. At its sole discretion, the State may consider a solution that includes any of these deliverables or consider deliverables not originally listed.
An offeror must highlight any requirement in Section 3 or Section 4 that the offeror’s proposed deliverables cannot comply with, and the offeror must provide any suggested “work-around” to the requirement in question or a future date that the offeror will be able to comply with the requirement.
4.1 The offeror’s proposal must include a:
• Project Management Plan
• Project Schedule
• Risk Management Plan
• Data Conversion Plan, if applicable
• Requirements Traceability Matrix
• Communication Plan
• Testing Plan
• Training Plan
• Go-Live/Cutover Plan
• Post-Implementation Support (or Maintenance and Operations Plan)
In addition, the offeror’s proposal must include how its proposed deliverables will meet the following IT requirements (General, State Hosted, and Vendor Hosted). If the offeror’s proposal includes an option for a state hosted solution and an option for a vendor hosted solution, the offeror must provide a separate response for each proposed solution and how each solution will meet the requirements in Sections 3 and 4.
4.2 GENERAL IT REQUIREMENTS
4.2.1 Artificial Intelligence Use
The offeror must provide an explanation of its use of Artificial Intelligence, both in its proposed solution and the development lifecycle of the proposed solution. This requirement includes the offeror’s use of Generative AI (GenAI) tools/products. For GenAI tools/products, the offeror must provide the following:
• GenAI model name, UPDATED OCTOBER 26, 2026 19
• product owner,
• product description (including purpose, functionality, and key characteristics),
• use case (or goal e.g. image recognition, natural language processing, text summarization),
• the intended information use (context for how information is used in the model) for the GenAI included in the offeror’s proposal,
• the geographical location of the tool, and
• how the offeror monitors and audits the tool’s compliance on use restrictions, data restrictions, legal compliance (non-discriminatory outputs), and biases in the tool’s outputs.
4.2.2 Hosting and Data Access Requirements
The State will own all data tables created as a result of the Agreement. The State must have the ability to manipulate data, run reports as needed, pull code tables, access raw data, and develop dashboards as needed through Microsoft Power BI, ESRI, Tableau, and associated platforms.
The offeror’s proposal must describe how the State can access data housed within the proposed solution for ingestion into a state data repository, encompassing available methodologies (e.g., application programming interface (API), flat file), data formatting, frequency of updates, and any inherent constraints. Additionally, the offeror’s proposal must provide a high-level architecture diagram, as part of the solution diagram as required by Section 6.7, explaining the proposed solution's data provision mechanism.
If available, the offeror must provide separate, complete proposals for the offeror’s proposed solution to be hosted by the offeror, by the State on its internal infrastructure, and on the State’s Azure cloud hosted tenant as a PaaS solution. If any of the hosting options is not available, the offeror must clearly state that in the offeror’s proposal and provide an explanation as to why the hosting option is not available.
4.2.3 Single Sign-On Requirements
If the offeror’s proposal includes a deliverable with a login component, the proposal must describe how the deliverable will integrate with the State’s standard identity management service single sign-on (SSO).
The State’s SSO supports the industry standard OAuth 2.0 protocol. This identity management will handle password recovery and multi-factor authentication (MFA). MFA is required for all application Administrators and may be required for other users. The State’s SSO requirement and links to Microsoft’s official documentation can be found at:
https://www.sd.gov/bit?id=bit_standards_single_sign_on.
If the offeror is not able to fulfill this identity management standard, the offeror’s proposal will be rejected from consideration.
https://www.sd.gov/bit?id=bit_standards_single_sign_on
UPDATED OCTOBER 26, 2026 20
4.2.4 SSO Logout Initiation Requirements
• The offeror’s deliverable must provide users with a clear and easily accessible logout mechanism (e.g., a “Logout” button/link).
• The logout functionality of the offeror’s deliverable must trigger a session-based logout process utilizing the sign-out endpoint found in the metadata document provided during implementation.
4.2.5 Session Timeout Requirements
• The offeror’s deliverables must allow for a customizable, State-defined inactive user session timeout period.
• The offeror’s deliverables must notify users of impending session expiration five minutes before the timeout occurs, providing users with the option to extend the session.
4.2.6 Session Termination on Browser Close Requirement
The offeror’s deliverables must clearly notify users that closing the browser window or tab is not a valid logout because the SSO session may remain active.
The notice must further notify users that they are responsible for explicitly logging out to ensure complete session termination.
4.2.7 Onboarding/Provisioning of Users Requirement
The offeror’s proposal must describe how new users are onboarded or provisioned into the deliverable. The offeror must provide an automated process for onboarding and offboarding users or must provide a process that requires minimal manual steps.
4.2.8 Interfaces and…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .