Single Source Purchases: Difference between revisions

From Appalachian State University Policy Manual
imported>Deaskc
imported>Deaskc
Line 45: Line 45:


== Revision Dates ==
== Revision Dates ==
Last modified 04/08/2011 08:55:49 AM by Matt McNaney

Revision as of 13:52, 20 July 2011

Policy 509.7

Introduction

You may copy this page's source to start a new policy page. Be sure to remove or overwrite the examples. Second level headings should NOT be altered.

Scope

Definitions

Definition phrase or word

Definition summary


Policy and Procedure Statements

Justification

On some highly technical items, there will be only one known source. Justification for a purchase of this type of item without competitive bidding must accompany the procurement request. The justification memorandum should be forwarded to the Director of Purchasing for approval and should give the following information:

  • Name and address of the suggested supplier.
  • Technical specifications which make the equipment unique.
  • Names and addresses of other vendors which make similar equipment, and details of the ways such equipment fails to meet required specifications.

Supporting Documents

Copies of all correspondence including any vendor quotations received in the selection of the special equipment should also accompany the procurement request.

Approval

If the request exceeds $150,000.00 in cost, the request will be forwarded to the State Purchase and Contract Division for processing. If the State Purchase and Contract Division concurs in the justification for the uniqueness of the item, the request will be presented to the State Board of Awards with the recommendation that the item be certified as "Single Source" and purchased after the Purchase and Contract Division has obtained prices in accordance with prescribed procedures.

Limited Use

This process is infrequently used since there is generally competition for almost any type of equipment or supplies used at the University.

Additional References

Authority

Contact Information

Effective Date

Revision Dates

Last modified 04/08/2011 08:55:49 AM by Matt McNaney