Often new 3rd Party systems are necessary to improve business operations. The selection and implementation of these technology tools is a critically important task and there are many questions to be answered before the purchase of any new system:
Can the business need be solved within any currently owned SPU systems?
Will new equipment need to be purchased and what are the initial and ongoing costs?
What effect, if any, will the application have on other departments or staff?
What are the annual savings costs and savings of the system, including estimated FTE cost in support and training?
How does adding the support of this new system affect available support for existing systems?
How will this system share data with other systems, such as Banner?
What state and federal regulations may impact SPU's usage of the system?
Computer and Information Systems staff can help guide you through this process with. See Project Intake for information about submitting a new project request to CIS.
Any new systems purchases must comply with theEnterprise Software Acquisition Policy to receive CIS support. It can be helpful to review and consider the requirements at the ideation phase of your product selection process. Technical review can also take weeks to months, so make sure to get started early.
Cloud or SaaS software takes special consideration. It usually comes with significant cost reduction, but also carries more risk. See the Cloud Computing Policy and review the SaaS Software Checklist for details on what to consider.
Any software purchase that requires any type of signed agreement must be reviewed by the Computer and Information Systems. This process can often take weeks to months, so make sure to get started early.
In Washington state, the sale of software and some associated services are taxed. Review the state's IT Tax Information page to help you estimate implementation and purchase costs.
If the new software or system needs Institutional Data or may generate new institutional data, please review the Campus Data Policy and Data Regulatory Compliance to understand the regulatory and policy requirements for the information you expect to use. If the data is steward or governed by a separate business unit, you must obtain approval to use that data from that unit. For example, to use student data, you need approval from the Office of the Registrar.