Summary
This article intends to guide Facilities and Campus Services (FCS) employees through the process of gaining additional licenses through the year in accordance with current IT Governance practices. Annual renewals may be necessary and routine, but off-schedule license changes, can be just as familiar if these steps are followed.
Body
Disclaimer: This article touches on guidelines for how the majority of software gets through the IT Governance Process and to procurement with minimal rewrites. Success, steps, and interactions may vary considering the type, scope and length of the project. If you have a question while working through this process, don't hesitate to ask the IT Liaison.
What's the difference between this and renewal?
This article intends to guide Facilities and Campus Services (FCS) employees through the process of gaining additional licenses through the year in accordance with current IT Governance practices. Annual renewals tend to be routine, expected, and prepared at least 2 weeks before the contract is scheduled to end. On the other hand, unexpected license increases can happen at any time and won't follow the same steps as a regularly scheduled renewal. There are several steps to determine which route will best suit your needs. Please use the following steps to troubleshoot getting access and ensure your departments licenses are grouped and renewed together.
Additional Licenses Process
There are several steps to determine which route will best suit your needs. To ensure the licenses are grouped and renewed together, please follow the steps in sequential order to troubleshoot.
- Check this CIT web page to see if Cornell University holds licenses for this product/service. Submit a ticket, if the search is successful.
- Find the Functional Admin/License Owner of the product and ask them if there are any available licenses.
- Contact the IT Liaison and ask whether the last statement of need was submitted for this product within the last year:
- If there is one, move onto the next step.
- If there was not one, follow up with the functional admin. They will have context on why it wasn’t created and if you can be added during the renewal.
- Determine if license(s) can be purchased using a Purchase Order or P-card?
- Purchase with an I Want Doc (IWNT): when there is a contract or a purchase order is needed. Include the following when applicable:
- Approved Statement of Need email.
- Technology Risk Assessment Results and supplemental documentation requested during this process.
- Web Accessibility Assessment Results and supplemental documentation requested during this process.
- Contract, Invoice, ITPSA or Order form from the vendor.
- Approved Project Charter, if needed.
- Purchase with a Pcard when no contract is needed/available. Include the following when applicable:
- Approved Statement of Need email.
- Technology Risk Assessment Results and supplemental documentation requested during this process.
- Web Accessibility Assessment Results and supplemental documentation requested during this process.
- Receipt from the vendor.