04.06.2014 Views

Purchasing Department - University of Connecticut

Purchasing Department - University of Connecticut

Purchasing Department - University of Connecticut

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Proposals must demonstrate an understanding <strong>of</strong> the scope <strong>of</strong> work and the ability to<br />

accomplish the tasks set forth and must include information that will enable the <strong>University</strong> to<br />

determine the proposer's overall qualifications.<br />

1.9.2 Proposals should be presented in a format that can easily be incorporated into a contract<br />

between the proposer and the <strong>University</strong> <strong>of</strong> <strong>Connecticut</strong>, encompassing the guidelines<br />

detailed in the Request for Proposal as required by the <strong>University</strong>.<br />

1.9.3 Each proposal must include a table <strong>of</strong> contents with page numbers for each <strong>of</strong> the<br />

required.<br />

All proposals must include a point-by-point response to this RFP. Each response must<br />

be cross-referenced to the corresponding numbered item in this RFP and described in as<br />

much detail as possible.<br />

Failure to respond to all points may be grounds for rejection. Likewise, failure to<br />

supply any information required to accompany the proposals may cause a rejection <strong>of</strong><br />

the proposal as non-compliant. The <strong>University</strong> reserves the right to request additional<br />

information and/or presentations, if clarification is needed.<br />

If you require additional space to completely answer any <strong>of</strong> the questions contained in<br />

this proposal document, include attachments and identify your response by page<br />

number, section heading, and specific section number.<br />

Proposals that do not substantially conform to the contents <strong>of</strong> the proposal request,<br />

consequently altering the basis for proposal comparison, may be disregarded and<br />

considered as unresponsive.<br />

1.9.4 All required original signatures must be affixed in Sections 9, 10, Bidder Contract<br />

Compliance Monitoring Report and the required Affidavits and Certifications.<br />

1.9.5 At the specified time stated in 1.9.1 above, all proposals received as stipulated, shall be<br />

publicly opened and dated. However, due to the complexity <strong>of</strong> the responses, only the<br />

names <strong>of</strong> the respondents will be read as no immediate decision will be made. All<br />

information will be confidential until after review and action by the Evaluation<br />

Committee. All interested parties are, however, welcome to attend the proposal<br />

opening.<br />

1.9.6 Confidential Information: Proposals are treated as confidential by the <strong>University</strong> until<br />

after the award is issued. At that time they become subject to disclosure under the<br />

Freedom <strong>of</strong> Information Act. If a respondent wishes to supply any information which it<br />

believes is exempt from disclosure under the Act, which respondent should summarize<br />

such information in a separate envelope and each page submitted should clearly state<br />

"Confidential," but otherwise be presented in the same manner as the Proposal.<br />

However, any such information is provided entirely at the respondent's own risk and the<br />

<strong>University</strong> assumes no liability for any loss or damage which may result from the<br />

<strong>University</strong>'s disclosure at any time <strong>of</strong> any information provided by the respondent in<br />

connection with its proposal.<br />

1.10 Completed RFP's: It is the intent <strong>of</strong> the <strong>University</strong> to select a vendor which is capable <strong>of</strong><br />

supplying all services outlined in the RFP specification.<br />

9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!