Contract Models
Michael Anthony Waara
Overview
Contract Models are the primary way contracts are categorized, identified, and reported on. These models are just names for the primary purpose of the contract, or what exactly is being purchased. There are minor field differences between certain models, but the underlying workflow (and the Contract Life Cycle) is the same for each model. For consistency, use only the following models when categorizing a contract. The table below includes descriptions of the different contract models with some examples of existing contracts.
Contract Models Table
| Model | Description |
|---|---|
| Equipment | Contracts covering the recurring purchase of equipment. |
| Hardware Maintenance | Contracts covering the maintenance of hardware. |
| Insurance (Not used by OIT) | Used by UCI Procurement for all contracts relating to the purchase of insurance. |
| Lease | Contracts where the object of the contract is leased rather than purchased. |
| Membership | Subscriptions to recurring membership expenses. Examples include:
|
| Purchase Order (Not used by OIT) | Used by UCI Procurement when a formal contract that includes a security review and supporting documentation is not necessary. |
| Service Contract | Contracts covering the purchase of services that support the functions of OIT, but are not maintenance contracts bound to an asset. Examples include:
|
| Software License/Subscription | Contracts covering the purchase of perpetual software licenses or other software subscriptions. |
| Software Maintenance | Contracts covering the maintenance of software. |
In the event that a contract falls under multiple models (e.g. a purchase of hardware including the first year of maintenance), a decision must be made to either pick one model or set up two contract records. It is better practice to do the latter and set up two contract records–one record for the purchase of the asset, and another for the maintenance of that asset.
Revision History
| Revised By | Revised Date | Approved By | Approved Date | Comments |
|---|---|---|---|---|
| Michael Anthony Waara |
| Chris Nelson |
| Finalized contract models according to technical specifications for changes to the contract module and added definitions. |
| TBD | TBD | Initial draft. |
GUIDE STATUS: PUBLISHED
Navigation