RFP Document.pdf

Dated 10/10/25

STATE OF SOUTH DAKOTA

South Dakota State University

Purchasing Office 1451 Stadium Road – Box 2201

Morrill Hall Room 304 Brookings, SD 57007

Request for Proposal (RFP) for SDBOR Enterprise AI Platform Implementation Services

PROPOSALS ARE DUE NO LATER THAN July 14, 2026, by 5:00pm CDT

RFP #: SDBOR06262026 Buyer: Karen Bravek EMAIL: Karen.Bravek@sdstate.edu

READ CAREFULLY

FIRM NAME: AUTHORIZED SIGNATURE:

ADDRESS: TYPE OR PRINT NAME:

CITY/STATE: TELEPHONE NO:

ZIP (9 DIGIT): FAX NO:

E-MAIL:

PRIMARY CONTACT INFORMATION

CONTACT NAME: TELEPHONE NO:

FAX NO: E-MAIL:

1.0 GENERAL INFORMATION

1.1 PURPOSE OF REQUEST FOR PROPOSAL (RFP)

The South Dakota Board of Regents (SDBOR) is seeking a partner to support the implementation of a secure, scalable enterprise AI platform that provides students, faculty, researchers, and staff across all institutions with access to approved AI capabilities through a shared technology foundation.

The platform must support institution-specific branding and delegated administration while remaining aligned with SDBOR’s existing identity, security, and governance framework. It must also provide centralized visibility, control, and enforcement capabilities to support systemwide governance processes.

The Boise State AI Platform (AgentCore Public Stack) will serve as a baseline reference for expected functionality and user experience.

SDBOR will provide a prebuilt AWS landing zone. The selected partner will be expected to validate this environment, provide recommended improvements, and work with SDBOR to implement agreed-upon changes. This includes deploying and configuring the platform, integrating identity and security controls, and supporting operational readiness to enable transition of ownership to SDBOR.

Governance ownership will remain with SDBOR. The partner’s role is focused on technical implementation, validation, and enablement. The resulting platform should support a shared enterprise model with delegated institutional control, align with current SDBOR security and operational practices, and be designed to accommodate future expansion and integration.

1.2 ISSUING OFFICE AND RFP REFERENCE NUMBER

The SDSU Purchasing Office is the issuing office for this document and all subsequent addenda relating to it, on behalf of the State of South Dakota, South Dakota Board of Regents, through the Regental Information Systems (RIS). The reference number for the transaction is RFP #SDBOR06262026. This number must be referred to on all proposals, correspondence, and documentation relating to the RFP.

1.3 SCHEDULE OF ACTIVITIES (SUBJECT TO CHANGE)

RFP Publication June 26, 2026 Offeror Questions Due July 2, 2026, by 10:00am CDT Responses to Offeror Questions July 8, 2026, by 5:00pm CDT Proposal Submission July 14, 2026, by 5:00pm CDT Anticipated Award Decision/Contract Negotiation July 31, 2026

1.4 SUBMITTING YOUR PROPOSAL

All proposals must be completed and received in the SDSU Purchasing Office via email to Karen Bravek, SDSU Purchasing Manager at Karen.Bravek@sdstate.edu by the date and time indicated in the Schedule of Activities. Proposals received after the deadline will be late and ineligible for consideration. The proposal submission email MUST have a subject line that includes the appropriate RFP Number and Open Date.

Example:

REQUEST FOR PROPOSAL #SDBOR06262026 Opening 7-14-2026

This information is the ONLY information that should appear in the Subject Line of your email.

Any other information could cause your bid to be rejected.

All proposals must be signed by an officer of the responder, legally authorized to bind the responder to the proposal. Proposals that are not properly signed may be rejected.

No proposal shall be accepted from, or no contract or purchase order shall be awarded to any person, firm or corporation that is in arrears upon any obligations to SDSU/State of South Dakota, or that otherwise may be deemed irresponsible or unreliable by SDSU or 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 bidder shall attach an explanation to their offer.

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 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 an 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 SDCL 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.

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 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 OFFEROR INQUIRIES

Offerors may email inquiries concerning this RFP to obtain clarification of requirements. No inquiries will be accepted after the date and time indicated in the Schedule of Activities. Inquiries must be emailed to Karen Bravek at Karen.Bravek@sdstate.edu with the subject line “RFP

#SDBOR06262026 QUESTIONS”.

The State will respond to offeror’s inquiries (if required) via e-mail. In addition, all inquiries and the State’s response will be posted on the state’s e-procurement system. Offerors 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. Offerors will be notified in the same manner as indicated above regarding any modifications to this RFP.

1.11 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.12 LENGTH OF CONTRACT

The engagement is expected to be executed in a phased approach, aligned to key milestones for platform validation, implementation, and operational readiness.

The initial contract term will extend through June 30, 2027.

SDBOR reserves the option to extend the contract for up to one (1) additional year, based on project needs, partner performance, and mutual agreement.

1.13 GOVERNING LAW

Venue for any and all legal action regarding or arising out of the transaction covered herein shall be solely in the State of South Dakota. The laws of South Dakota shall govern this transaction.

1.14 DISCUSSIONS WITH OFFERORS (ORAL PRESENTATION/NEGOTIATIONS)

An oral presentation by an offeror to clarify a proposal may be required at the sole discretion of the State. However, the State may award a contract based on the initial proposals received without discussion with the Offeror. If oral presentations are required, they will be scheduled after the submission of proposals. Oral presentations will be made at the offeror’s expense.

This process is a Request for Proposal/Competitive Negotiation process. Each Proposal shall be evaluated, and each respondent shall be available for negotiation meetings at the State’s request.

The State reserves the right to negotiate on any and/or all components 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.0 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, along with any additional terms and conditions as negotiated by the parties:

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 services to be provided under the contract shall commence and terminate on mutually agreed upon dates. Terms for early termination shall be included in the agreement as negotiated by the parties.

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 State will not pay Contractor's expenses as a separate item. Payment will be made consistent with SDCL

ch. 5-26.

2.5 The Contractor agrees to indemnify and hold the State of South Dakota, its officers, agents and employees, harmless from and against any and all actions, suits, damages, liability or other proceedings that may arise as the result of performing services hereunder. This section does not require the Contractor to be responsible for or defend against claims or damages arising solely from errors or omissions of the State, its officers, agents or employees.

2.6 The Contractor, at all times during the term of this Agreement, shall obtain and maintain in force insurance coverage of the types and with the limits as follows:

A. Commercial General Liability Insurance:

The Contractor shall maintain occurrence based commercial general liability insurance or equivalent form with a limit of not less than $1,000,000.00 for each occurrence. If such insurance contains a general aggregate limit it shall apply separately to this Agreement or be no less than two times the occurrence limit.

B. Professional Liability Insurance or Miscellaneous Professional Liability Insurance:

The Contractor agrees to procure and maintain professional liability insurance or miscellaneous professional liability insurance with a limit not less than $1,000,000.00.

C. Business Automobile Liability Insurance:

The Contractor shall maintain business automobile liability insurance or equivalent form with a limit of not less than $1,000,000.00 for each accident. Such insurance shall include coverage for owned, hired and non-owned vehicles.

D. Worker’s Compensation Insurance:

The Contractor shall procure and maintain workers’ compensation and employers’ liability insurance as required by South Dakota law.

Before beginning work under this Agreement, Contractor shall furnish the State with properly executed Certificates of Insurance which shall 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 shall furnish copies of insurance policies if requested by the State.

2.7 While performing services hereunder, the Contractor is an independent contractor and not an officer, agent, or employee of the State of South Dakota.

2.8 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. Contractor shall report any such event to the State immediately upon discovery.

Contractor's obligation under this section shall 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. Contractor's obligation to report shall 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 shall not excuse or satisfy any obligation of 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 hereof, this Agreement may be terminated by the State at any time with or without notice. If termination for such a default is effected by the State, any payments due to Contractor at the time of termination may be adjusted to cover any additional costs to the State because of Contractor's default. 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 default by Contractor it is determined that Contractor was not at fault, then the Contractor shall 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. Termination for any of these reasons is not a default by the State nor does it give rise to a claim against the State.

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 shall be expressly identified as a part hereof, and be signed by an authorized representative of each of the parties hereto.

2.12 This Agreement shall be governed by and construed in accordance with the laws of the State of

South Dakota. Any lawsuit pertaining to or affecting this Agreement shall be venued in Circuit Court, Sixth Judicial Circuit, Hughes County, South Dakota.

2.13 The Contractor will comply with all federal, state and local laws, regulations, ordinances, guidelines, permits and requirements applicable to providing services pursuant to this Agreement, and will be solely responsible for obtaining current information on such requirements.

2.14 The Contractor may not use subcontractors to perform the services described herein 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, state and local laws, regulations, ordinances, guidelines, permits and requirements and will adopt such review and inspection procedures as are necessary to assure such compliance.

2.15 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 shall 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.16 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.17 Any notice or other communication required under this Agreement shall be in writing and sent to the address and individuals indicated in the Agreement, or such authorized designees as either party may from time to time designate in writing. Notices or communications to or between the parties shall be deemed to have been delivered when mailed by first class mail, provided that notice of default or termination shall be sent by registered or certified mail, or, if personally delivered, when received by such party.

2.18 In the event that any court of competent jurisdiction shall hold any provision of this Agreement unenforceable or invalid, such holding shall not invalidate or render unenforceable any other provision hereof.

2.19 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 herein, this Agreement constitutes the entire agreement with respect to the subject matter hereof.

2.20 The State affords equal opportunity to individuals in its employment, services, programs, and activities in accordance with applicable federal and state laws, including requirements related to accessibility of electronic and information technology.

The Contractor, and any subcontractors, shall:

A. Deliver all services, configurations, and solution components provided as part of this engagement in reasonable compliance with applicable accessibility standards, including but not limited to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, Section 508 of the Rehabilitation Act, and any successor standards, as applicable;

B. Ensure that any customizations, configurations, or user interface elements introduced by the Contractor do not degrade or negatively impact the accessibility of the underlying platform;

C. Provide SDBOR with accessibility testing results and documentation for Contractor-delivered components upon request;

D. Promptly respond to and assist in resolving accessibility-related issues identified by SDBOR that are attributable to the Contractor’s work;

E. Acknowledge that failure to address accessibility issues within a reasonable timeframe may result in termination of the Agreement without penalty to the State.

3.0 SCOPE OF WORK

The selected partner will work with the South Dakota Board of Regents (SDBOR) system office, through Regental Information Systems (RIS), to validate, implement, and operationalize an enterprise AI platform aligned to SDBOR’s existing architecture, security, identity, and governance framework.

SDBOR, through RIS, will retain ownership and operational control of the AWS environment and the centralized AI platform on behalf of all institutions. The resulting platform is intended solely for internal use by SDBOR institutions, including students, faculty, researchers, and staff, and is not intended for external commercialization or resale.

SDBOR will provide a prebuilt AWS landing zone and foundational design components. The partner will be responsible for validating this environment, recommending improvements, and working with SDBOR to implement agreed-upon changes.

Phase 1 of this engagement is limited to deployment and configuration of the Boise State AI Platform (AgentCore Public Stack) and the capabilities available within that baseline solution. The partner is not expected to design or implement net-new platform capabilities beyond this baseline during Phase 1. The platform architecture must, however, support future phased enhancements.

3.1 AWS Foundation and Landing Zone

Assess and validate the AWS organization and account structure implemented by SDBOR, ensuring alignment to a centralized, multi-institution operating model and appropriate separation across environments

Review the landing zone design, including security guardrails, logging, monitoring, and governance controls, and confirm readiness to support Phase 1 deployment

Validate VPC and network architecture, including segmentation, connectivity, and access patterns required for the baseline platform

Evaluate the infrastructure-as-code approach and provide recommendations focused on standardization, maintainability, and Phase 1 readiness

Assess cost management capabilities, including allocation by institution and service and visibility into consumption

Identify gaps and risks impacting Phase 1 delivery and provide prioritized recommendations Work with RIS to implement agreed-upon changes necessary to support Phase 1 deployment

3.2 Identity and Access Management

Integrate the platform with SDBOR’s federated identity architecture, including Microsoft Entra ID, existing SSO patterns, and institutional MFA controls, in coordination with RIS identity teams

Implement a role-based access control model aligned to baseline platform capabilities, supporting systemwide administration, institutional administration, and end-user roles

Support group-based and attribute-based access mapping as required for the baseline solution Enable delegated institutional administration for assistants, knowledge repositories, and content, while RIS retains control of core identity services Ensure SDBOR retains centralized administrative control, including feature enablement, policy enforcement, and override capability

3.3 AI Platform Deployment and Configuration (Phase 1)

Assess the Boise State AI Platform (AgentCore Public Stack) and deploy and configure the platform within the RIS-managed AWS environment Implement platform capabilities consistent with the Boise State baseline, including:

o Multi-model AI integration and centralized model management o Assistant creation, management, sharing, and discovery o Shared prompt libraries and reusable templates with administrative controls o Knowledge-based assistants with document ingestion, source attribution, and role-based access control o Administrative dashboards and standard configuration patterns Configure baseline observability capabilities, including usage analytics, reporting, and cost tracking by user, assistant, and institution Ensure implementation adheres to the Boise State reference architecture and avoids custom extensions beyond agreed Phase 1 scope

3.4 Institutional Experience and Multi-Tenant Architecture

Implement a multi-tenant architecture aligned to the baseline platform supporting seven institutional AI experiences: Board of Regents, BHSU, DSU, NSU, SDSMT, SDSU, and USD Configure institution-specific branding, including logos, color schemes, announcements, and featured assistants Define and implement a domain strategy appropriate for Phase 1, supporting institution-branded domains where feasible or a centralized approach where required Ensure the platform supports a shared enterprise model with delegated institutional configuration and management

3.5 Security and Compliance

Implement core security controls required for Phase 1, including encryption at rest and in transit, secure administrative access, and logical separation of institutional data Configure logging and monitoring aligned to baseline capabilities, including user activity, administrative actions, API interactions, and assistant activity Integrate platform logs with RIS security operations where supported, including Microsoft Sentinel and Red Canary Implement AI interaction logging (prompts and responses) with appropriate access controls for audit and investigative purposes Configure data handling controls to enforce document ingestion restrictions, repository access controls, and prevention of cross-institution data exposure Ensure the platform supports alignment with FERPA, HIPAA, GLBA, and applicable SDBOR policies, with SDBOR retaining responsibility for governance and compliance enforcement

3.6 Operational Readiness and Transition

Develop a platform operations model aligned to RIS ownership, including monitoring, alerting, and day-to-day management processes Define backup, recovery, and availability approaches appropriate to the baseline platform Establish cost management processes for ongoing visibility and control Provide structured knowledge transfer to RIS platform administrators, identity teams, and security operations teams Define and execute a transition plan from partner-led implementation to RIS operational ownership at the conclusion of Phase 1 Provide recommendations for ongoing support and future enhancement approach to be considered in subsequent phases

3.7 Phase 1 Deliverables

AWS landing zone assessment and validation report with prioritized recommendations for Phase

Identity integration architecture and authorization model aligned to baseline capabilities Deployed and configured AI platform based on the Boise State reference implementation Administrative and assistant management framework Multi-tenant architecture and institutional branding implementation Security and logging integration approach Reporting and analytics capabilities available within the baseline platform

Operational documentation, including runbooks and procedures Knowledge transfer completion and transition plan

3.8 Future Phases and Expansion Considerations

Following completion of Phase 1, additional phases will be defined to expand platform capabilities. The Phase 1 architecture must support future enhancements, including:

Enterprise knowledge services Enterprise data integrations (e.g., Banner, D2L, Microsoft 365, data warehouse platforms) MCP-enabled data access, including server deployment and configuration Agentic AI capabilities, including workflow automation and orchestration RAG ingestion pipelines and enterprise document ingestion frameworks Expanded institutional adoption

Scope, priorities, and timelines for these capabilities will be defined through mutually agreed-upon milestones following Phase 1 completion.

3.9 Governance Alignment

SDBOR, through RIS, retains responsibility for governance frameworks, AI model approval processes, data classification, and risk management

The platform must provide the visibility, control, and enforcement capabilities necessary to support these processes

3.10 Success Criteria

Target completion for Phase 1: mid-September 2026 AWS landing zone validated and operational Security guardrails implemented Federated authentication integrated in coordination with RIS Boise State platform deployed and operational Seven institutional AI experiences available Administrative reporting and analytics in place Cost management controls established Platform ownership transitioned to RIS operational teams

Ongoing milestones and additional phases will be defined and agreed upon between SDBOR and the selected partner for the remainder of the engagement to support incremental platform enhancements aligned to SDBOR’s AI roadmap.

4.0 PROPOSAL REQUIREMENTS AND COMPANY QUALIFICATIONS

4.1 The offeror is cautioned that it is the offeror's sole responsibility to submit information related to the evaluation categories and that the State of South Dakota is under no obligation to solicit such information if it is not included with the proposal. The offeror's failure to submit such information may cause an adverse impact on the evaluation of the proposal.

4.2 Offeror's Contacts: Offerors and their agents (including subcontractors, employees, consultants, or anyone else acting on their behalf) must direct all of their questions or comments regarding the RFP, the evaluation, etc. to the buyer of record indicated on the first page of 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/or exclusion from specific procurements. Offerors and their agents who have questions regarding this matter should contact the buyer of record.

4.3 Provide the following information related to at least three previous and current service/contracts, performed by the offeror’s organization, which are similar to the requirements of this RFP.

a. Name, address and telephone number of client/contracting agency and a representative of that agency who may be contacted for verification of all information submitted;

b. Dates of the service/contract; and

c. A brief, written description of the specific prior services performed and requirements thereof.

4.4 Offerors must demonstrate relevant experience supporting AWS-based solutions aligned to the requirements of this RFP.

a. The offeror must be an active AWS Partner in good standing at the time of proposal submission and throughout the duration of the engagement;

b. Provide a brief description of the offeror’s experience with AWS environments, including multi-account architectures, identity integration, and secure application deployments;

c. Describe experience working in environments where the customer retains control of the AWS platform, identity services, and governance model.

4.5 Opensource Licensing Requirements: Offerors must acknowledge and comply with the licensing terms associated with the Boise State AI Platform (AgentCore Public Stack), which is licensed under the PolyForm Noncommercial License 1.0.0.

a. The offeror must acknowledge that the platform is intended for internal use by SDBOR institutions and is not to be used for commercial purposes;

b. The offeror must confirm that their proposed approach complies with the terms of the PolyForm Noncommercial License, including restrictions on commercial use;

c. The offeror must acknowledge that their role is limited to implementation, configuration, and support services for SDBOR and does not grant rights to commercially distribute, resell, or reuse the solution outside of this engagement;

d. The offeror must identify any licensing considerations, risks, or additional requirements associated with their proposed approach.

5.0 PROPOSAL RESPONSE FORMAT

5.1 Interested vendors must email their complete document in a Word or PDF format to Karen Bravek, SDSU Purchasing Manager at Karen.Bravek@sdstate.edu, per section 1.4 – Submitting your Proposal. The proposal should be page numbered and should have an index and/or table of contents referencing the appropriate page number.

5.2 All proposals must be organized and tabbed with labels for the following headings:

5.2.1 RFP Form. The State’s Request for Proposal form (1st page of RFP) completed and signed.

5.2.2 Executive Summary. The one-to-two-page executive summary is to briefly describe the offeror's proposal. This summary should highlight the major features of the proposal. It must indicate any requirements that cannot be met by the offeror. The reader should be able to determine the essence of the proposal by reading the executive summary.

Proprietary information requests should be identified in this section.

5.2.3 Detailed Response. This section should constitute the major portion of the proposal and must contain at least the following information:

5.2.3.1 A complete narrative of the offeror's assessment of the work to be performed, the offeror’s ability and approach, and the resources necessary to fulfill the requirements. This should demonstrate the offeror's understanding of the desired overall performance expectations.

5.2.3.2 A specific point-by-point response, in the order listed to each requirement in the

RFP. The response should identify each requirement being addressed as enumerated in the RFP.

5.2.3.3 A clear description of any options or alternatives proposed.

5.2.4 Cost Proposal. Cost will be evaluated independently from the technical proposal.

Offerors may submit multiple cost proposals. All costs related to the provision of the required services must be included in each cost proposal offered.

See section 7.0 for more information related to the cost proposal.

6.0 PROPOSAL EVALUATION AND AWARD PROCESS

6.1 After determining that a proposal satisfies the mandatory requirements stated in the Request for Proposal, the evaluator(s) shall use subjective judgment in conducting a comparative assessment of the proposal by considering each of the following criteria:

6.1.1 Specialized expertise, capabilities, and technical competence as demonstrated by the proposed approach and methodology to meet the project requirements;

6.1.2 Resources available to perform the work, including any specialized services, within the specified time limits for the project;

6.1.3 Record of past performance, including price and cost data from previous projects, quality of work, ability to meet schedules, cost control, and contract administration;

6.1.4 Availability to the project locale;

6.1.5 Familiarity with the project locale;

6.1.6 Proposed project management techniques;

6.1.7 Ability and proven history in handling special project constraints;

6.1.8 Demonstrated experience and qualifications related to AWS-based solution delivery, including status as an AWS Partner and experience supporting enterprise, multi-account environments with customer-managed governance and identity models; and

6.1.9 Demonstrated understanding of the Phase 1 scope and ability to implement the Boise State AI Platform (AgentCore Public Stack) consistent with baseline capabilities, while avoiding unnecessary customization or expansion beyond defined requirements.

6.2 Experience and reliability of the offeror's organization are considered subjectively in the evaluation process. Therefore, the offeror is advised to submit any information which documents successful and reliable experience in past performances, especially those performances related to the requirements of this RFP.

6.3 The qualifications of the personnel proposed by the offeror to perform the requirements of this RFP, whether from the offeror's organization or from a proposed subcontractor, will be subjectively evaluated. Therefore, the offeror should submit detailed information related to the experience and qualifications, including education and training, of proposed personnel.

6.4 The State reserves the right to reject any or all proposals, waive technicalities, and make award(s) as deemed to be in the best interest of the State of South Dakota.

6.5 Award: The requesting agency and the highest ranked offeror shall mutually discuss and refine the scope of services for the project and shall negotiate terms, including compensation and performance schedule.

6.5.1 If the agency and the highest ranked offeror are unable for any reason to negotiate a contract at a compensation level that is reasonable and fair to the agency, the agency shall, either orally or in writing, terminate negotiations with the contractor. The agency may then negotiate with the next highest ranked contractor.

6.5.2 The negotiation process may continue through successive offerors, according to agency ranking, until an agreement is reached or the agency terminates the contracting process.

7.0 COST PROPOSAL

7.1 Offerors must provide a detailed cost proposal for delivery of the services described in this RFP. Pricing should be clearly presented and aligned to the proposed approach.

7.2 The cost proposal must, at a minimum, include a breakdown of costs for Phase 1 implementation, including all services required to meet the Scope of Work and Success Criteria defined in this RFP.

7.3 Offerors may propose pricing using a fixed fee, time and materials, or hybrid approach. The pricing structure must be clearly defined and include all assumptions.

7.4 The cost proposal must include, at a minimum:

a. Total cost for Phase 1 implementation;

b. Breakdown of costs by major activity or deliverable (e.g., AWS validation, platform deployment, identity integration, operational readiness);

c. Hourly rates by role, if applicable;

d. Estimated level of effort by role, if applicable;

e. Description of any one-time and recurring costs associated with implementation services;

f. Identification of any assumptions, dependencies, or exclusions that may impact pricing.

7.5 Offerors are not required to include ongoing platform consumption costs (e.g., AWS usage, AI model consumption, or other usage-based operational costs) as part of the cost proposal. Such costs will be managed separately by SDBOR following deployment.

7.6 Offerors must provide indicative pricing for future phases, including expanded platform capabilities and/or ongoing support services. This may include estimated pricing models, rate structures, or example cost ranges for anticipated services.

7.7 Pricing provided for future phases will be used for planning and comparative purposes only and will not be the primary basis for evaluation of Phase 1 cost proposals.