04.06.2014 Views

Purchasing Department - University of Connecticut

Purchasing Department - University of Connecticut

Purchasing Department - University of Connecticut

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.2 Discontinued Items<br />

3.3 New Items<br />

a.) The vendor must report in writing when a core item is discontinued or otherwise<br />

unavailable.<br />

b.) The vendor must provide exact or higher value replacements for any discontinued<br />

items.<br />

c.) The vendor must document replacements for any discontinued items and provide<br />

samples to purchasing for approval.<br />

d.) The vendor must report discontinued or unavailable core items within ten (10) days<br />

after the item is discontinued or unavailable.<br />

The respondent shall provide a detailed narrative describing how it will meet the requirements identified<br />

above.<br />

In addition to the items currently available to the respondent, the <strong>University</strong> expects to have<br />

access to new items from either currently represented manufacturers or new sources <strong>of</strong> items<br />

that are added to the respondent's array <strong>of</strong> product <strong>of</strong>ferings. The Contractor must notify the<br />

participating <strong>University</strong> <strong>of</strong> new products which become available during the term <strong>of</strong> the<br />

contract at least annually. The same pricing discounts which apply to similar contract items<br />

shall apply to the new items.<br />

The respondent shall provide a detailed narrative describing how it will meet the requirements identified<br />

above.<br />

3.4 Order Placement & Web Content Control<br />

All catalog orders will be placed electronically through the selected vendor’s dedicated punch-out<br />

catalog website through the <strong>University</strong>’s Husky Buy application with the possible exception <strong>of</strong><br />

non-catalog orders, bulk orders, special and/or customized products which will be placed via<br />

traditional purchase order. These orders will be faxed or e-mailed to the selected supplier.<br />

Contractors must be able to restrict excluded items as noted in Section 3.0. Telephone and/or fax<br />

orders will not be required and should not be accepted. Please refer to Section 3.14 for Technical<br />

Requirements for Dedicated Website.<br />

a.) If an order or release cannot be delivered within the appropriate time frame as indicated<br />

under 3.1.13 <strong>of</strong> this Section, the Contractor should immediately notify the end user via e-<br />

mail, when delivery will be made as well as provide a reasonable explanation for the<br />

delivery delay. If the ordering campus has not been so notified <strong>of</strong> a delay in delivery or is<br />

not provided with a reasonable explanation for such delivery delay, the ordering campus<br />

may cancel the order with the Contractor and purchase the item(s) elsewhere and the<br />

Contractor shall be liable for any additional cost over the Contractor's net contract price<br />

<strong>of</strong> the item(s).<br />

b.) If a critical item is out <strong>of</strong> stock at the time the order is to be placed and cannot be<br />

delivered within the time frame necessary to meet the user's requirement, even if the<br />

item would be deliverable within the allowable number <strong>of</strong> working days noted in the<br />

RFP specifications, the <strong>University</strong> reserves the right to place the order with an alternate<br />

source. In such an instance, the Contractor will not be liable for any additional cost<br />

over the Contractor's net contract price <strong>of</strong> the item(s).<br />

The respondent shall provide a detailed narrative describing how it will meet the requirements<br />

identified above.<br />

16

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

Saved successfully!

Ooh no, something went wrong!