3 |
Gather critical information regarding the purchase(s). |
Critical information may include:
- What is your intended use of the software?
- Historical background/has software been previously purchased?
- Are other University departments using the software or similar software?
- What is the functionality of the software?
- How long do you anticipate using the software?
- Do you want to maintain access to the most current version(s) offered, or is only a fixed version needed?
- What level of technical support is required? (5x7, 7x24, etc.)
- How many people will use the software?
- Do you anticipate the number of people using the software to increase or decrease over the lifecycle of the contract?
- Is there another unit of measure of use that makes better sense than per user?
- Do you expect users who are not Yale employees or students to use the software?
- Is the purchase federally sponsored?
- Is sensitive data involved such as health or personal data (HIPAA or PII).
- If so, additional assessments or documentation such as a Business Associate Agreement (BAA) and Data Addendum (DA) may be needed.
- Note: Sourcing Managers can help support departments with the BAA.
- What is the desired timeline for the purchase?
- If moving from existing software, what time & effort needed to move to new software?
- Do you expect the software to run on a single platform or are multiple platforms (mobile, cloud, etc.) required?
- Do you expect to use only in the United States, or will international rights be required?
- Are there any specific requirements for interoperability (i.e. the ability for the software to exchange and make use of information)?
- Justification for supplier selection (criteria).
- Additional key decision makers, project team members.
|