UConn Inst for AI Innovation Tech Sol RFP CDR010826.pdf

PDF 266 KB Posted

Attached to
AI Innovation Institute Technology Solutions
Solicitation number
CDR010826
Issued by
Connecticut

About this file

Summary

This is a Request for Proposal (RFP) issued by the University of Connecticut for AI Innovation Institute Technology Solutions. The University seeks a qualified technology solutions provider to design, build, supply, install, support, and continuously enhance an advanced AI computing resource to serve as foundational infrastructure for the newly established AI Innovation Institute. The requested system must include approximately 400 latest-generation GPUs and a similar number of AI accelerator nodes, delivering computing power exceeding 30 PFLOPS with approximately 15PB of related storage, supported by high-speed redundant data fabric. The proposal may include on-premise, cloud, or hybrid deployment modalities. Proposers must provide 24/7/365 support with a 4-hour onsite response time for physical equipment issues and 4-hour response time for cloud service incidents, along with a three-year warranty with options to extend for minimum of two additional years. The pre-proposal conference is scheduled for January 21, 2026 at 2:30 PM ET, with questions due by February 10, 2026 at 2:00 PM ET and proposals due February 18, 2026 at 2:00 PM ET. The contract term is four years with five additional one-year extension options, for a total potential term of nine years. The University reserves the right to make a single award or multiple awards as deemed in its best interest.

The pricing proposal must include separate, clearly itemized cost breakdowns for the baseline AI computing environment and General Research Enclave, plus incremental costs for implementing the HIPAA Enclave and Federal Compliance Enclave (NIST SP 800-171/FISMA). For each enclave, proposers must identify one-time implementation and configuration costs, recurring operating costs, any per-user or usage-based charges, and compliance-specific expenses. The proposal evaluation criteria weight technical capability and demonstrated success at 25 percent, system architecture and project plan at 25 percent, financial proposal at 30 percent, and value-added considerations at 20 percent. Proposers must provide references from comparable-sized customers, with preference for higher education institutions. The University requires all vendors to acknowledge adherence to the Vendor Code of Conduct policy. All proposals must be submitted through the HuskyBuy portal, and any exceptions to RFP or template contract terms must be declared in detail within the proposal.

View the file

Other files

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

RFP # CDR010826 Page 1

REQUEST FOR PROPOSAL

AI Innovation Institute Technology Solutions

RFP# CDR010826

Proposal Release Date

January 8, 2026

Pre-Proposal Conference

January 21, 2026, 2:30 PM (ET)

Proposal Due Date

February 18, 2026; 2:00 PM (ET)

UConn Procurement 3 Discovery Drive, Unit 6076 Storrs, CT 06269-6076 Phone: 860.486.2619

RFP # CDR010826 Page 2

Table of Contents

1.0 Introduction

2.0 Background - About UConn

3.0 Scope of Work

4.0 Instructions to Proposers

5.0 Submission Instructions:

6.0 Standard RFP Requirements

7.0 Standard Contract Terms and Conditions

RFP # CDR010826 Page 3

1.0 Introduction

The University of Connecticut (hereinafter referred to as the “University”) is seeking proposals from qualified and experienced suppliers (hereinafter referred to as "vendor", "proposer", "bidder", “firm”, or "respondent") to enter into a contract(s) to provide the described services to the University.

2.0 Background - About UConn

The University is a Land, Sea, and Space Grant consortium institution which occupies over 4,302 acres, enrolls over 30,000 students, and produces over 7,000 undergraduate, graduate, and professional degrees annually. The main campus is located in Storrs, Connecticut, and regional campuses are located in the following Connecticut towns: Avery Point, Hartford, Stamford, and Waterbury. Its academic health center, UConn Health, is located in Farmington, Connecticut. Detailed University demographics are available via the following link: 2025 Fact Sheet.

The University has played a pivotal role in Connecticut’s economic growth since its founding in 1881.

With an annual economic impact of $7.8 billion and a workforce and student body population of more than 40,000, UConn drives innovation through research and industry collaboration. UConn is committed to fostering talent, advancing technological innovation, and bolstering the state’s economic landscape.

Aligned with its strategic plan emphasizing research excellence, innovation, and responsible AI development and application, UConn seeks to establish an Institute for Artificial Intelligence (AI) Innovation. The institute will serve as a hub for AI research, development, education and workforce development, promoting economic competitiveness, growth, and responsible use across the following areas:

1. Computer Science and Technology - AI/ML development, natural language processing, cybersecurity, and Quantum-AI interaction;

2. Financial Technologies - innovations for finance, insurance, real estate and other fields;

3. Health and Life Sciences - pharmaceutical sciences, genetics/genomics, computational biology, precision medicine and digital twins;

4. Engineering and architecture;

5. Advanced Manufacturing - system engineering, robotics, and augmented reality (AR);

6. Social Impact and Economic Development - psychology, economics, and public policy; and,

7. Art and Humanities.

UConn’s objective is to contract with a qualified technology solutions provider to design, build, supply, install, support, and continuously enhance an advanced AI computing resource. The AI computing resource will serve as the foundational infrastructure for the AI Innovation Institute and address the broader AI needs of the University. The resource is intended as a university-wide asset, supporting all departments and disciplines—including, but not limited to, STEM, arts and humanities, Healthcare and every field where AI has relevance. The resource must enable equitable access for all stakeholders, https://uconn.edu/annual-fact-sheet

RFP # CDR010826 Page 4 ensuring no scholarly endeavor, trade, or profession is overlooked, while advancing education and engagement around the ethical, responsible, and equitable use of AI across the university community.

3.0 Scope of Work

This solicitation is based on a solutions-based model, rather than a highly prescriptive specifications approach. The awarded proposer will be expected to deliver state-of-the-art AI resources and supporting software solutions aligned to the establishment of UConn’s Institute for Artificial Intelligence (AI) Innovation and the identified objectives of the University.

Hardware and Software Needs:

The University has identified the following minimum hardware and software needs for the AI System:

A combination of the latest generation GPUs and AI accelerator (AIA) nodes Approximately 400 GPUs (latest generation) and a similar number of AIAs Overall goal of computing power exceeding 30 PFLOPS (RPEAK) Overall goal of related storage (approximately 15PB) A high-speed, redundant data fabric supporting within the cluster Software and ML models for different applications (as described in the RFP) 24/7/365 support with a 4-hour onsite response time for physical equipment issues, and a 4-hour response time for cloud service incidents A three-year warranty with the option to extend for additional years, available for a minimum of two years.

System Modality:

The proposal may include three different modes: On premise, Cloud, and Hybrid (a combination of on premise and cloud) solutions.

Technical & Programmatic Support:

The awarded proposer will be responsible for supplying the personnel to manage and operate the AI resource for UConn’s use on an ongoing basis. The anticipated support includes set-up and initial configuration, and continuous administration, monitoring, optimization, and support of the resource for the life of the contract. The awarded proposer will run the AI resource as a managed service, ensuring stability, security, and performance on a 24/7 basis. The proposal must describe the proposed software in detail and the maintenance strategy, including OS version and software upgrades/patches and related strategy for service interruption mitigation. The proposal must also articulate proposer’s assumptions related to support by UConn personnel, if any.

At a minimum, the awarded proposer’s team must include the following roles:

• Application Developers

• System Administrators

• Software Engineers

RFP # CDR010826 Page 5

• Data Scientists

• Network and Security Engineers

Required Features:

The proposal must address the following features:

• Immediate cloud services scaled to meet current needs. The cloud services may be part of a longer-term hybrid environment based on service level needs throughout the life of the agreement

• Installation, system testing, and validation of multiple environments (test, UAT, production) and multiple modalities

• Services architected with high availability in mind, ensuring maintenance of individual components without disrupting the continuity of the overall service

• Secure Multi-Enclave Architecture: The proposed AI computing environment must be designed to support multiple, logically segregated security enclaves with distinct compliance profiles. At a minimum, proposers must design and describe an environment that includes:

• General Research Enclave: An environment intended for standard academic and research workloads that do not require special regulatory protections

• HIPAA Enclave: An environment designed to support research involving Protected Health Information (PHI) and to enable the University to meet its obligations under HIPAA and associated regulations. The Enclave must support HIPAA compliance, including technical, administrative, and physical safeguards

• Federal Compliance Enclave: An environment designed to support workloads requiring compliance with federal data security frameworks, including at least NIST SP 800-171 and FISMA. The Enclave must support implementation of the required controls, including boundary protections, logging/monitoring, incident response, and access controls

• Each Enclave must be logically segregated (and physically segregated where appropriate) with clearly defined security boundaries, identity and access management, network segmentation, data storage, logging/monitoring, and backup/restore processes. The proposal must explicitly describe:

• The technical architecture of each Enclave;

• How users and data move between Enclaves, if at all; and

• How the design supports the University’s ability to meet HIPAA, NIST SP 800-

171, and FISMA requirements for applicable workloads.

• Use of HIPAA Enclave for Non-HIPAA Workloads

• The proposer may, at their discretion, propose hosting non-HIPAA research workloads within the HIPAA-compliant Enclave, provided all HIPAA requirements remain fully satisfied. However, the proposal must present the HIPAA Enclave as a separately scoped environment and provide a distinct cost breakdown associated with enabling and operating HIPAA compliance.

• Technical Support and Warranty

RFP # CDR010826 Page 6

• Periodic system refreshes based on technological advances

Pricing Proposal:

In addition to the directions provided in RFP Section 6.8 below, the pricing proposal is expected to address the following:

Proposers must provide a separate, clearly itemized cost breakdown for:

• The baseline AI computing environment and General Research Enclave;

• The incremental costs associated with implementing and operating the HIPAA Enclave; and,

• The incremental costs associated with implementing and operating the Federal Compliance

Enclave (NIST SP 800-171 / FISMA).

For each Enclave, proposers must identify, at a minimum:

• One-time implementation and configuration costs;

• Recurring operating costs (e.g., managed services, monitoring, compliance support, licensing);

• Any per-user, per-project, or usage-based charges; and

• Any additional costs specific to achieving or maintaining compliance with HIPAA, NIST SP 800-

171, and/or FISMA.

Costs must be presented in a way that clearly distinguishes the base environment from the marginal cost of adding and maintaining each additional Enclave.

Value-Added Considerations – Future Collaboration:

Proposers are invited to include in the proposal any value-added features or additional services or approaches to assisting the university in realizing the following goals:

• AI Ecosystem Development: Fostering a network of industry partners, researchers, and stakeholders to drive AI skill democratization, applied AI commercialization, and regional research advancements;

• Joint Research Programs: Establishing and executing a collaborative research program focused on challenging problems and large grant opportunities involving transformative AI solutions;

and/or,

• AI Education & Training: Developing and implementing a comprehensive AI curriculum that includes education, workforce training, and skill development initiatives.

The proposal must include sufficient information for the University to evaluate the mutual benefits of such a collaboration. Any collaboration will be codified in a collaboration agreement separate and distinct from the award of the contract for AI computing services.

Contract Term:

Initial term of 4 years, plus five additional 1-year extensions, or any part or combination thereof, for a total potential contract term of 9 years. (Proposer may propose an alternate contract term or extension

RFP # CDR010826 Page 7 options aligned to financial proposal.)

It is the University’s intent to make a single award as a result of this RFP. However, the University reserves the right to make multiple awards if it is deemed by the University to be in the University’s best interest to do so.

4.0 Instructions to Proposers

4.1 RFP Schedule

RFP EVENT DATE(S)*

RFP Issue/Release January 8, 2026

Pre-Proposal Conference January 21, 2026, 2:30 PM (ET)

Question Deadline February 10, 2026; 2:00 PM (ET)

Proposal Due Date & Time February 18, 2026; 2:00 PM (ET)

Proposer Presentations or Demonstrations [optional] March 2026

*Subject to change as deemed necessary by the University.

** A Pre-Proposal Conference will be conducted via virtual meeting platform. Directions for the Pre-Proposal Conference will be posted in the “Buyer Attachments” for this opportunity in the HuskyBuy platform 48 hours in advance. Pre-Proposal Conference attendance is optional for prospective proposers but highly encouraged.

4.2 Point of Contact: All communications and/or inquiries regarding this RFP must be submitted through the HuskyBuy portal. Failure to adhere to this provision may result in a Proposer being declared ineligible, proposal rejection, or Sourcing Event cancellation. The University will not respond to any request for clarification received after the Deadline for Proposer Questions has expired.

Under no circumstances may any proposer or its representative contact any employee or representative of the University regarding this Sourcing Event prior to the closing date. Strict adherence to this important procedural safeguard is required. Any violation of this condition may result in the proposer being considered non-compliant and ineligible for award.

RFP # CDR010826 Page 8

4.3 Communications: Upon formal issuance of a RFP, the University and Proposer(s) will cease all informal communications relevant to the RFP and assume a formal, in writing, communication posture until a binding contractual agreement is executed with the selected Proposer(s), all other Proposers have been notified as to their RFP status, or when the University formally rejects all proposals and cancels the RFP process. Failure to adhere this provision may result in a Proposer being declared ineligible, proposal rejection, or RFP cancellation.

4.4 Addenda: Addenda are issued in response to Proposer questions and/or University clarifications and revisions to the RFP. Addenda are incorporated into the RFP and may be incorporated along with the RFP into any resulting contract. Failure of a Proposer to retrieve any addendum shall not relieve the Proposer of any responsibility for complying with the terms thereof. All addenda must be acknowledged by the Proposer in the HuskyBuy portal. Failure to acknowledge any and all addenda may be grounds for rejection of the proposal response.

4.5 Pre-Proposal Conference: A Pre-Proposal Conference is a scheduled meeting which may occur during a public RFP solicitation process. The purpose of the meeting is to provide interested Proposers with an opportunity to: pose questions related to the RFP process and request Scope of Work information and/or clarification. Pre-Proposal Conference attendance for the opportunity is optional for prospective proposers but highly encouraged. [See the Solicitation Schedule above for specific schedule details and requirements.]

4.6 Proposal Presentations: The University evaluation committee may require proposal presentations or extended demonstrations. If invited to present or demonstrate, the Proposer will be responsible for making all the necessary arrangements and will bear all costs associated with the presentation or demonstration. Presentations or demonstrations will be scheduled at the discretion of the University and within the time allocated in the RFP schedule when possible.

[See the Solicitation Schedule for specific schedule details]. Presentation or demonstration invitations will only be issued to those firms selected to participate in the presentation or demonstration phase of this RFP and will include the meeting date, time, location, duration, and associated agenda/requirements outlining specific proposal areas for discussion, as outlined at the University’s discretion.

4.7 Campus Visitor Parking: Intentionally omitted.

4.8 Proposal Evaluation Criteria: All proposals will be evaluated by an evaluation committee, using the specific evaluation criteria listed in the table below. Each criterion has been assigned a value representing the relative weight. The evaluation committee will conduct a comprehensive review and analysis of the proposals received and recommend which proposal(s) is the most advantageous to the needs of the University.

RFP # CDR010826 Page 9

Evaluation Criteria Weight

Technical Capability & Demonstrated Success (implementation of AI computing services to a research-driven customer base) 25

System architecture, project plan, and timeline 25

Financial proposal (pricing, short-term and long-term cost-effectiveness, economic factors, and feasibility) 30

Value-added considerations 20

Total 100

In the event the evaluation committee elects to conduct presentations or extended demonstrations by any one or more of the proposers, the evaluation committee will re-assess the proposal of each proposer that remains in the evaluation process by adjusting overall rank order based on the proposal, the supplemental content received during each such event, and the assessment of most advantageous overall to the needs of the University.

5.0 Submission Instructions:

5.1 RFP Due Date and Time: Proposals are due at the date and time stated in the Solicitation

Schedule above. Any proposal received after the stated due date and time will be rejected.

Mailed, hand-delivered, facsimile, emailed, or other physical proposals will not be accepted under any circumstances.

5.2 Submittal: The entire Proposal, including all mandatory requirements, attachments, or supplemental material must be submitted using the HuskyBuy portal. Elaborate proposals, in the form of brochures or other presentation materials beyond what is necessary to present a complete and effective proposal, are not desired and should not be included. The narrative responses in the HuskyBuy portal should be complete and comprehensive, with a corresponding emphasis on being concise and clear. Any materials that a supplier feels are needed to provide clarity to their proposal should be included as attachments to the proposal.

6.0 Standard RFP Requirements

6.1 Definitions

6.1.1 “Request for Proposals (RFP)" means all documents, whether attached or incorporated by reference, utilized for soliciting proposals. Awards made as a result of an RFP shall be based upon “Competitive Negotiation”.

6.1.2 "Competitive negotiation" means a procedure for contracting for supplies, materials, equipment or contractual services, in which proposals are solicited from qualified suppliers

RFP # CDR010826 Page 10 by a request for proposals, and changes may be negotiated in proposals and prices after being submitted.

6.1.3 “Addenda” means written and/or graphic instructions issued by the University prior to the receipt of proposals that modify or interpret the Request for Proposal documents by addition, deletions, clarification, or corrections.

6.1.4 "Proposer" means a person, firm or corporation submitting a proposal in response to a Request for Proposal.

6.1.5 “Contractor” means any business that is awarded, or is a subcontractor under, a contract or an amendment to a contract with a state contracting agency under statutes and regulations concerning procurement, including, but not limited to, a small contractor, minority business enterprise, an individual with a disability, as defined in section 4a-60, or an organization providing products and services by persons with disabilities.

6.1.6 “Non-Acceptance of Proposal” means another proposal was deemed more advantageous to the University or that all proposals were rejected.

6.1.7 “Offer” or “Proposal” means the Proposer’s response to this Request for Proposal.

6.1.8 “Services” shall mean all services described within the scope of this RFP.

6.1.9 “Agreement” shall mean the contract issued as a result of this Request for Proposal.

6.1.10 “CT-based Businesses” shall be a firm that is: (i) a business entity organized, headquartered and operating in the State of Connecticut for at least one year prior to the date of bid submission; or (ii) a business entity that is authorized to do business in Connecticut, maintains an operating location in Connecticut, and has generated over 50% of its annual gross revenues each year, over the past five (5) years prior to the date of bid submission, from work on projects located in Connecticut.

6.1.11 “Joint Venture” in this sourcing context refers to firms that may have familiarity within particular areas but may not be subject matter experts in all necessary areas; therefore, the University welcomes joint venture proposals.

6.1.12 “SBE/MBE Firm” shall refer to a certified Small Business Enterprise/Minority Business Enterprise firm that meets the qualifications as determined by legislation, Connecticut General Statute 4a-60g (Supplier Diversity Statue) as amended by Public Act 11-229.

6.1.13 "University" or “UConn” or a pronoun used in its place shall mean the University of Connecticut main campus at Storrs, Connecticut as well as its five regional campuses and the Cooperative Extension Offices.

6.1.14 “UConn Health” or “UCH” shall mean University of Connecticut Health and its affiliates.

6.2 Proposal Understanding: Proposers must demonstrate: an understanding of the statement of work (SOW), the ability to accomplish the tasks set forth; and must include information that will enable the University to determine the proposer's overall qualifications.

6.3 Rendering of Service: Each Proposer must respond to, and be capable of, supplying all services outlined in the RFP specification.

RFP # CDR010826 Page 11

6.4 Expiration of Proposals: Proposals shall remain in effect from the RFP due date and time for a minimum period of 180 days.

6.5 Rights Reserved: The University reserves the right to cancel this solicitation, to reject any or all proposals received (or any part thereof without penalty), to waive informalities or irregularities, to seek clarification of any proposal and communicate with a proposer related to a request for clarification, and to award a contract not based solely on the lowest cost, but based on a Proposal which, in the sole opinion of the University, best fulfills or exceeds the requirements of this RFP and is most advantageous to the University. Firms subject to Non-Acceptance of Proposal shall be notified after a binding contractual agreement between the University and the selected Proposer exists or after the University has rejected all proposals.

6.6 Modification of Proposals: Proposals may be modified and re-submitted in the HuskyBuy portal up to the due date and time designated for receipt of proposals provided they conform to these terms and conditions.

6.7 Withdrawal of Proposals: Proposals may be withdrawn from the HuskyBuy portal up to the due date and time designated for receipt of proposals.

6.8 Pricing: The Proposal must include a complete statement of the Proposer’s financial proposal and supplemental materials relevant to the financial proposal as deemed necessary by the Proposer. In the competitive process, the University will not advise a Proposer on the content of the financial proposal.

6.9 Sales Tax Exemption: In accordance Conn. Gen. Stat. §12-412(1)(A), the University is exempt from local, state, and federal excise taxes.

6.10 Independent Price Determination: Proposer warrants, represents, and certifies that:

6.10.1 The proposed costs have been arrived at independently, without consultation, communication, or agreement for the purpose of restricting competition as to any matter relating to such process with any other organization or with any competitor.

6.10.2 Unless otherwise required by law, the proposed costs have not been knowingly disclosed by the Proposer on a prior basis directly or indirectly to any other.

6.10.3 No attempt has been made, or will be made, by the Proposer to induce any other person or firm to submit or not to submit a proposal for the purpose of restricting competition.

6.11 Review of References: The Proposer is required to provide references from customers of comparable size and scope as the University. The University is particularly interested in references that are institutions of higher education.

RFP # CDR010826 Page 12

6.12 Good Faith Negotiation: If the University and selected Proposer(s) are unable to reach a mutually agreeable contract, the University reserves the right to abandon negotiations and commence negotiations with the next highest ranked Proposer. The University will be the sole judge of the suitability of the proposed Agreement(s).

6.13 Incorporation of Proposal: Proposals submitted in response to this RFP may, at the University’s option, be incorporated into the executed contract.

6.14 “NO SUBSTITUTE”: Unless qualified by the provision “NO SUBSTITUTE”, the use of the name of a manufacturer, brand, make or catalog designation in specifying an item does not restrict proposers to the manufacturer, brand, make or catalog designation identification. This is used simply to indicate the character, quality and/or performance equivalence of the commodity desired, but the commodity on which proposals are submitted must be of the same or better character, quality and/or performance equivalence that it will serve the purpose for which it is to be used equally as well as that specified. In submitting a proposal on a commodity other than as specified, proposer shall furnish complete data and identification with respect to the alternate commodity bidder proposes to furnish. Consideration will be given to proposals submitted on alternate commodities to the extent that such action is deemed to serve best the interests of the State. If the proposer does not indicate that the proposed commodity is other than specified, it will be construed to mean that the proposer proposes to furnish the exact commodity described. Any substitutions must meet or exceed all specification requirements and must receive approval in writing from the appropriate party at the University prior to any order being filled.

6.15 Ownership of Samples: Intentionally Omitted.

6.16 Proposal Preparation: The University assumes no cost for proposal preparation and/or submission.

All costs are borne by the Proposer at Proposer’s expense.

6.17 Confidential Information: The University treats Proposals as confidential until after the award is issued. At that time, they become subject to disclosure under the Freedom of Information Act. If a Proposer wishes to supply any information, which it believes is exempt from disclosure under the Act, Proposer should summarize such information in a separate file with a filename containing the word "Confidential" and a watermark or stamp titled “Confidential”, but otherwise be presented in the same manner as the Proposal. However, any such information is provided entirely at the Proposer’s own risk and the University assumes no liability for any loss or damage which may result from the University's disclosure at any time of any information provided by the Proposer in connection with its proposal.

The proposer and its employees will not disclose information acquired in connection with the performance of services under this agreement which is proprietary or confidential in nature to the University without written permission from the University. This confidentiality will continue to be

RFP # CDR010826 Page 13 in effect even after the contract has been completed or terminated for any reason. Some projects may require additional confidentiality documentation or agreements, which will vary according to the University’s needs, legal requirements and scope of work.

6.18 Freedom of Information: While the University may be willing to agree not to disclose the information proactively, the University is subject to the Connecticut Freedom of Information Act, found in Chapter 14 of the Connecticut General Statutes, which may require disclosure, should the document be requested with limited exceptions. Two such exceptions that might apply are as follows: (1) Conn. Gen. Stat. sec. 1-210(b)(24) permits the University to withhold records related to the procurement process while bidding and contract negotiations are underway (this moratorium is temporary and lasts only until the contract has been executed or negotiations are abandoned); and Conn. Gen. Stat. sec. 1-210(b)(5) permits the University to withhold records in its possession in the event they contains trade secrets (or intellectual property). In the event that the University determines that Conn. Gen. Stat. sec. 1-210(b)(5) may apply to a given request for the records in question, the responsibility to substantiate claims that said records would reveal trade secrets and meet the exemption requirements is borne by the owner of said trade secrets, not the University.

Further, if the entity seeking access to the documents challenges the University’s withholding of the document, said owner may be required to prove at the Freedom of Information Commission and/or in a Court of Law, that the release of said trade secrets would be harmful to the owner of the intellectual property or properties in question.

6.19 Conflict of Interest: The Proposer shall disclose and identify to the University, with its proposal, any relationships, which may constitute a potential conflict of interest with the University of Connecticut Purchasing Department, or any other University organizations or departments for the purpose of determining whether a conflict of interest exists. All such disclosures require acceptance/approval action on the part of the University, who shall determine, in its sole discretion, whether an impermissible conflict exists.

6.20 Ethics and Compliance Reporting/Whistleblower Protection: The University Office of Audit, Compliance, and Ethics is responsible for handling anonymous ethics and compliance reporting.

Any person who is aware of unethical practices, fraud, violation of state laws or regulations, or other concerns relating to University policies and procedures can report such matters anonymously using the information provided on their website.

6.21 Corporate Social Responsibility: In furtherance of its longstanding commitment to fundamental human rights, to the dignity of all people, and to the environment, the University requires all Vendors to adhere to the "Vendor Code of Conduct" policy. Please provide acknowledgement of this University policy and any additional pertinent information.

6.22 Minor Defects: If, during the solicitation and/or evaluation process, the University determines that a particular mandatory requirement may be modified or waived and still allow the University to http://policy.uconn.edu/?p=2718

RFP # CDR010826 Page 14 obtain goods/services that substantially meet the intent of this RFP, the mandatory requirement will be modified or waived for all proposers, and all proposals will be re-evaluated in light of the change.

6.23 Notification of RFP Status: Upon completion of the RFP review process, all Proposers will receive an RFP status notification. This notification covers three outcomes: No Further Consideration, Selected for Presentation or Demonstration, or Intent to Award.

6.24 Debriefing: Requests for debriefing by Proposer will be accommodated upon request.

6.25 OSHA Compliance: All items to be furnished shall meet all applicable local, state, and federal requirements of the Occupational Safety and Health Act. If any at any time, items or services covered under this RFP become non-compliant with applicable law, the Proposer or Contractor shall notify the University’s Chief Procurement Officer or Director of Procurement immediately by email.

6.26 Advertising/Licensed Merchandise/Sponsorship Opportunities: The Proposer agrees, unless specifically authorized in writing by the University, that it will have no right to use the University’s name, seal, mark of any kind (including logos), and its officials and/or employees in any advertising, publicity, or promotion including, but not limited to, any expression or implication of endorsement by the University.

6.27 Award: A contract will be awarded to the Proposer(s) whose proposal(s) is deemed to be the most advantageous to the University, in accordance with the criteria set forth within the RFP, taking into account the quality of the goods or services to be supplied, conformance with specifications, delivery terms, price and financial considerations, administrative costs, past performance, warranty, and financial responsibility.

6.27.1 The University may:

6.27.1.1 reject the proposal of any Proposer who is in default of any prior contract or is guilty of misrepresentation or any Proposer with a member of its firm in default or guilty of misrepresentation.

6.27.1.2 correct inaccurate awards resulting from clerical or administrative errors in accordance with and pursuant to the Regulations of Connecticut State Agencies.

6.27.1.3 make an award contingent upon the successful Proposer’s execution of the applicable required State of Connecticut certifications and affidavits.

6.27.1.4 award by item, groups of items or total bid; to reject any and all proposals in whole or in part, and waive any informality or technical defects if, in its judgment, the best interests of the University will be served.

RFP # CDR010826 Page 15

6.28 Exceptions to RFP and/or Template Contract Terms and Conditions: All exceptions to, deviations from, or inability to comply with the requirements set forth in the RFP or the University’s template contract terms and conditions must be declared and outlined in detail in the Proposal. Failure to do so will prevent the proposer from asserting an inability to comply with the terms or conditions later.

7.0 Standard Contract Terms and Conditions

The successful Proposer will be required to enter into a written contract with the University of Connecticut. The University’s template contract for this opportunity is available for download on the HuskyBuy portal and is incorporated herein by reference. Bidders are directed to carefully review the terms and conditions, as they will become part of any subsequent agreement and award.

7.1. Contract Status: The response to this RFP will be considered an offer to contract. Final negotiations on the highest evaluated offer will be conducted to resolve any differences and informalities. After final negotiations, the University will issue an acceptance of the proposal offer.

7.2. Contract Format: The resulting contract will be the product of negotiations and will be the entire agreement between the University and the Proposer, superseding and rescinding all prior agreements relating to the subject matter thereof. All of these documents signed by both parties and approved by the Office of the Attorney General will constitute the final contract. The University may also consider a request to utilize a Proposer’s template contract. To request a modification to the University’s template contract, or to propose the use of the Proposer’s template contract, the Proposer must identify the exception(s) or include its template contract in the Proposal for consideration in final contract negotiation.

7.3. Contract Modification: All changes to the contract must be agreed to, in writing, by both parties prior to executing any change.

7.4. Contract Assignment or Subcontract: The resulting contract shall not be assigned, transferred, or sublet in whole or in part without the prior written approval of the University.

7.5. Contract Commencement: The contract will commence upon execution of the aforementioned formal agreement and final approval by the Office of the Attorney General. The Project covered under the contract will be based on the specific University requirements or requests. The University can neither project nor guarantee a specific volume of business over the term of any contract that may result from this RFP.

7.6. Proposer Default: In the event of default by the Proposer, the University reserves the right to procure the commodities and/or services from other sources and hold the Proposer liable for any excess cost occasioned thereby. If, however, public necessity requires use of material or supplies not conforming to the specifications, they may be accepted, and payment therefore shall be made at a proper reduction in price.

RFP # CDR010826 Page 16

7.7. Payments under a Contract Award:

7.7.1. Under no circumstances shall the successful Proposer begin to perform under the contract prior to the effective date of the contract. All payments shall adhere to the payment terms negotiated in the contract award.

7.7.2. Cash discounts may be offered by the proposer for prompt payment of invoices. Such discount will not be taken into consideration in determining the low bidder but will be taken into consideration in awarding tie bids. The discount period will be computed from the date delivery is accepted at the destination or from the date the correct invoice is received by the consignee, whichever is the later date.

7.7.3. Payment terms shall be 2% 15 days, net 45 days unless otherwise noted in the bidder’s proposal. Terms other than those indicated above will be subject to University approval.

7.8. Evaluation of Performance: During or after the term of any contract or other agreement that results from this RFP process, the University may conduct evaluations of the successful Proposer’s performance including, but not limited to equipment, staffing, supplies and services. The successful Proposer may be requested to provide quality performance metrics and must cooperate with the University in any such evaluations and work with the University to correct any deficiencies noted.

7.9. Responsibilities of the Proposer:

7.9.1. Observing Laws and Regulations: The Proposer shall keep fully informed of and shall faithfully observe all laws, national and state, and all ordinances and regulations affecting responsibility to the University, or affecting the rights of supplier's employees, and must protect and indemnify the University, its officers, and agents against any claims of liability arising from or based on any violation thereof.

7.9.2. Representations: Each firm, by submitting a proposal, represents that it:

7.9.2.1. Has read and completely understands the proposal documents and all issued amendments or addenda; and

7.9.2.2. is totally familiar with the conditions under which the work is to be performed including but not limited to availability and cost of labor and materials.

7.9.3. Purchase Orders and Sub-Proposers: Purchase Orders and payments will only be issued to the Proposer. It is the Proposer’s responsibility to issue Purchase Orders, schedule services and pay all sub-Proposers and partners directly.

7.10. Advertising/Sponsorship Opportunities: In submitting a proposal, the Proposer agrees, unless specifically authorized in writing by the University on a case by case basis, that it shall have no right to use, and shall not use, the name of the University of Connecticut, its officials or employees, or the marks of the University (e.g., wordmark, seal, logos), a) in any advertising, publicity, marketing, or promotion; nor b) to express or imply any endorsement of agency’s services; nor c) to use the name of the state, its officials or employees or the University marks in any manner (whether or not similar to uses prohibited by subparagraphs (a) and (b) above) except only to manufacture and deliver in accordance with this agreement such services as are hereby contracted by the University. Should the Proposer be interested in pursuing a formalized sponsorship agreement with the University, which may include advertising benefits and use of

RFP # CDR010826 Page 17

University marks, contact UConn Procurement at the conclusion of this solicitation process for details on how to pursue such a relationship.

1.0 Introduction
2.0 Background - About UConn
3.0 Scope of Work
4.0 Instructions to Proposers
5.0 Submission Instructions:
6.0 Standard RFP Requirements
7.0 Standard Contract Terms and Conditions

File details come from the government source that posted it. Updated .