RFP Document.docx

STATE OF SOUTH DAKOTA

INFORMATION TECHNOLOGY (IT) RFP

(Department of Health- 615 E. 4th Street, Pierre, SD 57501)

Rural Health Data Atlas- Data Visualization and Analysis Platform

PROPOSALS ARE DUE NO LATER THAN August 10,2026

RFP #: 26-09RHT-021 STATE POC: Dr. Josh Clayton EMAIL: doh.datamodernization@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:

Version 1.1 August 29, 2016 1

1 General Information

1.1 Purpose of Request for Proposal (RFP)

1.1.1 Background:

The South Dakota Rural Health Data Atlas is a state-led initiative to transform how rural communities access and use health data. Today, critical health data is siloed across numerous systems, requiring communities, hospitals, Tribal Nations, and state agencies to navigate multiple systems and request processes to obtain a complete picture of local health. This fragmentation limits data-driven planning and slows response to emerging chronic disease concerns. To address these challenges, the South Dakota Department of Health (SD DOH) is developing a publicly-accessible, cloud-based platform that consolidates health data into a single, interactive environment. The Rural Health Data Atlas will integrate datasets from South Dakota’s health agencies and other publicly available sources into an intuitive platform featuring maps, charts, tables, and point-and-click analysis tools.

The result will be a centralized, state owned Microsoft Azure tenant cloud-based data visualization and distribution platform designed to modernize sharing and exploration of health data. The platform will integrate diverse datasets into a secure, user-friendly environment that supports advances visualizations, role-based access control, real-time ingestion, and accessibility compliance.

1.1.2 Goals and Objectives:

The Rural Health Data Atlas will enable access to health data and support data-driven decision-making, including serving as a point of dissemination of Rural Health Transformation outcome measures. The platform will empower:

· Hospitals to analyze local health trends, justify funding requests, and inform service delivery.

· Community coalitions to identify service gaps, plan interventions, and measure short- and long-term impact.

· State agencies to target resources toward preventable health issues and support coordinated public health action.

· Rural health clinics to strengthen value-based care, risk stratification, and proactive patient management and outreach.

· Tribal nations to design data-informed programs addressing local health outcomes.

· Academica and Research Organizations to easily access state data to perform analysis that will empower public health policies and initiatives.

1.1.3 Description of Components or Phases:

The selected vendor must employ a project management approach that will satisfy the scope of work and incorporate all activities described in the RFP. The selected vendor shall adjust the project management approach or project schedules, as necessary, to collaborate with the Department to successfully execute the project.

1.1.4 Scope of Components or Phases:

The following outlines year one activities to provide a scope of general project activities for a proposed start date of Oct 9, 2026.

· Develop a project plan, technical architecture, and data governance roles by Oct 22, 2026.

· Establish user personas, core design components, and finalize wireframes by Oct 30, 2026.

· Conduct a comprehensive Information Inventory System and establish intake standards by Oct 30, 2026.

· Set up the necessary infrastructure, including cloud services and security policies, by Nov 6, 2026.

· Deploy the MVP, ingest and validate data, and verify the platform by Jan 14, 2027.

· Complete UAT with trained staff and incorporate feedback by Jan 28, 2027.

· Launch the MVP for external users and execute the communications plan by Feb 5, 2027.

1.2 Issuing Office and RFP Reference Number

The Department of Health (“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#26-09RHT-021. 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:

1.4 Letter of Intent

All interested offerors must submit a Letter of Intent to respond to this RFP.

The Letter of Intent must be submitted to the Agency via email atdoh.datamodernization@state.sd.us by the date and time indicated in Section 1.3 Schedule of Activities. Please place the following in the subject line of your email: “Letter of Intent for RFP#26-09RHT-021”.

1.5 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 doh.datamodernization@state.sd.us . The email, including attachments, must be limited to 20MB in size.

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

1.7 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.8 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.9 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 and debar a business under SDCL § 5-18D-12.

1.10 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.11 Questions Regarding RFP

All written questions should be sent to: doh.datamodernization@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#26-09RHT-021”. 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.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.

1.13 Length of Contract

The length of the contract will be for a term of 1 year(s). The State will have the opportunity to renew the contract annually for up to 4 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.

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 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 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 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 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 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.21 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.22 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.23 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.24 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.25 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

3.1 Functional Requirements

3.1.1 Self-Service Platform (No Code Required)

· Platform must provide a 100% self-service, no code end-user experience.

· Platform must use a state determined and owned URL domain.

· User interface must remain:

· Intuitive, with straightforward navigation

· Accessible with no to minimal training

· Align with human-centered design principles.

· Contain logical user workflows

3.1.2 Multi Source Data Integration

All the data sources below (See Appendix D for indicator samples) would include metadata and should be able to support ingestion, curation and integration data from:

· SD DOH (e.g., immunization, vital records, infectious disease)

· Department of Social Services

· Department of Human Services

· Federally curated datasets (CDC, HRSA, Census, etc.)

· Vendor will retrieve, curate and maintain access to relevant federally curated data sources as part of the solution.

· The vendor will be responsible for ensuring that the data is appropriately curated, standardized, and updated to maintain accuracy, consistency, and alignment with federal standards.

· Local datasets (county, region, multicounty collaborations) Additional requirements:

· Support manual and automated ingestion (e.g., scheduled or real-time)

· Support full and incremental updates

· Provide real time or near real time validation and error feedback

· Flat files, including CSV, Excel, fixed-width, and delimited files

· Modern data lake formats, including Parquet and other columnar storage formats

· Relational databases and database extracts

· APIs and web services

· Secure file transfer or secure upload mechanisms

· Cloud-hosted storage, including State-managed cloud environments, vendor cloud environments, and federally or externally hosted data repositories

· Streaming, real-time, or event-based data sources where applicable

3.1.3 Restricted and Role-Based Data

· Allow administrators to upload datasets restricted to specific audiences.

· Support differentiated access for public users, community partners, researchers, Tribes, and state agency staff.

· Platform must allow administrators to upload data that is restricted to certain users or groups.

· Must support Role-Based Access Control (RBAC) and differentiated internal/external permissions.

· Integrate with the state’s Single Sign-on ecosystem using OAuth 2.0 protocol with OpenID Connect (OIDC)

3.1.4 Extensibility

· Support for adding new pages/modules that integrate seamlessly

· Responsive design for various screen sizes and devices

· Includes: iPhone, Android and Desktop designs

· For iPhone minimum system requirements of iOS 16 or higher

· For Android minimum system requirements of Android 9 or higher

· Support for language accessibility

3.1.5 Section 508 and ADA Compliance

· Compliance with Section 508 of the Rehabilitation Act of 1973

· Compliance with Americans with Disabilities Act of 1990 and WCAG 2.1 Level AA standards

· Accessibility features must include:

· Screen reader compatibility

· Keyboard navigation

· High-contrast visual elements

3.2 Data Visualization Requirements

3.2.1 Visualization Types

The system must support configurable visualizations including:

· Geospatial maps (city, county, region, state; Tribal-trust lands)

· Choropleth maps with interactive features (e.g., interactive hover, pan, zoom)

· Bar charts, line charts, pie charts, histograms

· Scatterplots, bubble charts, indicator tiles

· Tables, rankings, custom dashboards

· Downloadable graphics (PNG) and raw data (CSV)

3.2.2 Interactivity & Customization

Platform must allow users to:

· Filter by geography, time, demographics, and health indicators

· Apply regression lines, show trends, explore relationships between variables

· Conduct multi dataset comparisons and correlation analysis

· Drill down into sub-geographies and subpopulations

· Dynamically updated visualizations based on user-selected parameters

3.2.3 Statistical Analysis

· Platform must apply appropriate statistical functions to data being explored.

· Should support regression, linear trends, rate/stabilization rules, and safeguards for small cell suppression (“data governance as code”).

· Optional: Ability to support advanced analytic methods, such as predictive modeling, Generative AI, machine learning, anomaly detection, classification, or clustering, where appropriate to the use case

3.3 Geospatial Analysis

· Must support geographic granularity at multiple levels: city, county, region, state, or user-defined geographies.

· Must handle layered datasets and partial geographies.

3.4 Search & Discovery

Platform must include:

· Fuzzy search

· Topic and location recommendations

· Advanced filtering

· Potential AI-driven search enhancements

3.5 Embedding & Sharing

· Visualizations must be embeddable in external websites via iFrames, embed codes, or APIs.

· Graphics (PNG) and raw data (CSV) must also be downloadable.

3.6 Collaborative Workspaces

· Individual and group User-created workspaces

· Must be able to upload and store data

· Must be able to download and share data within a workspace

· Visualizations must be shareable based on user roles

3.7 Training & Support

· Must provide role based training for administrators, super-users, and general users.

· Must include OnDemand training modules

· Detailed user guides, FAQs, training videos, and learning overlays.

· Contains walkthroughs for new users.

3.8 Optional Chatbot Functionality

· Preference for platforms that offer integrated chatbot support or a roadmap for future integration

3.9 System Sustainability

· Must provide an extensive system and dashboard sustainability plan to ensure the system will continue to be supported after the initial release.

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 proposed solution can be hosted by the offeror or in the State’s cloud environment, 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,

· 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 Technical Requirements – Artificial Intelligence (AI) Systems

4.2.3 The Offeror shall meet all technical requirements listed below. These requirements apply to all AI functionality, any AI used in the development or delivery of the solution, and any third party AI components.

4.2.4 AI Use Disclosure Requirements

The system shall disclose all uses of Artificial Intelligence (AI), including Generative AI, embedded anywhere in the proposed solution.

The Offeror shall identify all AI models, algorithms, training methods, and data sources used.

The Offeror shall document whether AI components operate locally, in a cloud environment, externally, or interact with State data.

The Offeror shall provide architectural diagrams showing AI data flows, inputs, outputs, and inference pathways.

4.2.5 Intellectual Property and Prompt/Data Ownership

All prompts, instructions, inputs, outputs, metadata, logs, and AI generated artifacts shall be owned by the State.

The system shall not claim ownership over State data or AI generated outputs.

4.2.6 Data Classification, Handling, and Privacy Requirements The system shall classify all State data handled or processed according to State data classification policies (Public, Sensitive, PII, PHI, FTI, CJI, PCI, FERPA).

The system shall not transmit, store, or process Sensitive or Confidential State data within any public or unauthorized AI model.

The Offeror shall provide documented data retention, retention windows, and destruction policies for all AI components and third-party AI providers.

The system shall prohibit the use of State data for AI model training or tuning unless explicitly authorized in writing.

The system shall comply with HIPAA, IRS FTI, CJIS, PCI DSS, FERPA, and any other applicable federal and State data regulations.

The Offeror shall provide documentation demonstrating how data sovereignty is enforced at the system and contractual level.

4.2.7 Data Residency and Sovereignty

All AI related data inference, processing, routing, and storage shall occur within the United States.

If any unavoidable international routing exists, the Offeror shall provide technical evidence that no State data is included and demonstrate compliant safeguards.

AI service endpoints shall restrict data storage, model inference, and API operations to U.S.-located infrastructure.

4.2.8 5. Security and Risk Controls The system shall support configurable data retention settings, including zero retention for AI prompts and outputs, where applicable.

AI components shall support auditability, including logging of decisions, inference events, and user interactions.

The Offeror shall provide information on vulnerability scanning, patching cadence, and exposure management practices specific to the AI components.

4.2.9 Algorithmic Transparency and Bias Mitigation

The system shall include mechanisms to detect, mitigate, and monitor algorithmic bias or disparate impact.

The Offeror shall document all training data sources, finetuning data, and model lineage.

The system shall provide explainability features (e.g., model output explanations, decision rationale) for all AI assisted actions.

The Offeror shall provide audit access to configuration files, model parameters (where feasible), and logs.

4.2.10 AI Feature Controls and Disablement

The system shall provide the ability to selectively enable, disable, or limit AI features at the tenant, agency, group, and user level.

The system shall support immediate disablement of AI features that violate State compliance requirements.

The Offeror shall provide an administrative interface for modifying AI functionality without requiring vendor intervention.

The system shall return the State’s data and/or securely dispose of all State data from AI prompts, instructions, inputs, outputs, metadata, logs, and AI generated artifacts.

4.2.11 Transparency, Auditability, and Logging

The system shall log all AI related inputs, outputs, data flows, and decisions.

The system shall support export of logs in machine readable formats.

The Offeror shall provide audit access for State authorized personnel for compliance and investigative purposes.

Logs shall support correlation identifiers to trace AI activity across systems.

4.2.12 Human Oversight, Safety, and Accuracy

The system shall ensure human review for all high risk or high impact AI decisions.

The Offeror shall document known limitations, hallucination risks, or rates, or model reliability characteristics.

The Offeror’s personnel shall be trained in responsible AI practices and safe operational use.

The system shall provide mechanisms for users to correct, override, or dispute AI-driven outcomes.

4.2.13 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.14 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.

4.2.15 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.16 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.17 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.18 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.19 Interfaces and Integration Requirements

The offeror’s proposal must describe how the deliverables can adapt to business necessary interfaces using widely adopted open APIs and standards. Additionally, the offeror must make available or expose software services that would enable third-party developers to interface other business applications. The offeror must publish documentation for the software services in question. The offeror’s proposal must include a detailed description of system capability.

The system must ensure that all system‑to‑system integrations and API traffic are routed through the State of South Dakota’s standard API Management platform. The solution must utilize the State’s API Management (APIM) tool as the authoritative API broker for publishing, securing, monitoring, throttling, and managing all APIs. No APIs may bypass the State’s APIM layer. The offeror will configure APIs in accordance with State standards, including required policies, authentication mechanisms, logging, and analytics as defined by the State’s API governance framework.

4.2.20 Web Application Vulnerability Scan Requirements

Any web-based deliverable must undergo a web application vulnerability scan (“Vulnerability Scan”). The Vulnerability Scan must identify misconfigurations or vulnerabilities such as those found in the OWASP Top Ten and must detail the certainty level of each finding.

Unless expressly indicated in writing, the State assumes all price estimates and bids are for the delivery and support of deliverables that will pass Vulnerability Scans. If the State determines that any aspect of the deliverable has security vulnerabilities that must be corrected, the State will inform the offeror of the nature of the issue and the offeror will be required to respond in writing regarding mitigation plans for the security vulnerabilities. If the deliverable does not pass the initial Vulnerability Scan or the offeror cannot provide a satisfactory Vulnerability Scan report, additional scans may be required to confirm the deliverable is secure.

State Hosted: For state hosted web-based deliverables, the Vulnerability Scan will be performed by the State and the offeror’s proposal should take that into consideration when responding to this RFP. As a condition of the resulting contract, the state hosted web-based deliverable will have to successfully pass the Vulnerability Scan prior to the deliverable being allowed to go in a production environment. Any offeror who responds to this RFP must accept such a contract term and must factor this security requirement into the offeror’s proposal.

Vendor Hosted: For vendor hosted web-based deliverables, any offeror who makes it to the “Tech Review” stage of the RFP process must provide the State a copy of the full report of the deliverable’s most recent Vulnerability Scan, a summary will not be accepted. The offeror should mark the vulnerability report as “Confidential” if it treats such a report as confidential information.