Student Affairs Technology Projects

Review both the Student Affairs Software Catalog and the IT Service Catalog first to try to identify an existing solution. The providers of the software and services listed in these catalogs have existing relationships with Student Affairs, UC Berkeley and/or the UC System.  If an existing technology solution can meet at least 80% of your requirements, it should be the selected solution.

• IT Service Catalog
• Student Affairs Software Catalog(link is external)

• The Strategic Initiatives Director(link sends e-mail) can be a thought partner to offer guidance and best practices as you explore solutions to your business challenges, as well as connect you with campus resources and other division partners that may have a similar technology need. Additionally, the Strategic Initiatives team can provide insight to currently queued and active projects as well as upcoming project request periods and best practices.

• Student Affairs Procurement can help you determine if a formal bid is required for your project. Typically, software and services that have been formally bid have better pricing, and less risky contract terms, and are negotiated faster than contracts that have not been formally bid. This will help to ensure departments receive quality software as a service, competitive pricing, and suppliers who adhere to UC Regents’ policies.

• RSSP staff should confer with Ingrid Hunt (ijbhunt@berkeley.edu(link sends e-mail)), Technology Planner for RSSP, on any prospective project requests. Guidance will then be provided to coordinate with the Strategic Initiatives Director and Student Affairs Procurement.

•  UHS staff should continue to follow their established internal processes.

• It might be a Project if…

• It is multi-departmental/cross-division.

• It requires hosting or programming resources from SAIT (i.e. it is not a cloud solution).

• It requires specialized hardware to connect to the campus network.

• It requires data from or integration with another campus system.

• It has an estimated project budget of $500,000 or more or an estimated annual operating expense of $250,000 or more (project required).

• It is probably NOT a Project if...

• It is an online service that will not require data from or integration with another campus system.

• It would not require resources outside of your department to implement.

• What problem is being solved? Has it been clearly defined? What teams and/or resources do you anticipate would be needed to accomplish this project? Who is the project’s Sponsor?(link is external)

• Resource: Berkeley IT’s definition of a project(link is external)

• Resource: Berkeley IT’s (link is external)definition of the problem(link is external)

• Note: SAIT Project Management differs in intake and prioritization from Berkeley IT’s TPO. Our definitions of project and problem, however, are the same.

• What features are required? What vendors have been considered? Do any vendors present unique advantages or offerings? What is the approximate 1st year/implementation pricing? What are the annual costs?

Resource: You may use this feature comparison template(link is external) to define requirements and compare vendor products.

Ask questions of potential vendors to see if they seem prepared to meet the Security/Privacy and Accessibility needs of the procurement process.

• Security/Privacy

• Ask potential vendors if they have completed a HECVAT(link is external) (Higher Education Community Vendor Assessment Toolkit). A vendor that has completed a HECVAT demonstrates attention to security and it is a good sign that they will be responsive during a vendor security assessment.

• If there is credit card data involved, ask potential vendors if they have a PCI DSS Attestation of Compliance from a Qualified Security Assessor (this is a third party attestation, not a self attestation).

• Ask potential vendors if they have a security plan they are able to share as part of a procurement process.

• Consider the business and/or data location of potential vendors. Vendors without a US presence can pose extra security risks and contractual challenges.

• Inquire with potential vendors and confirm that the data is not being used to generate income outside of the contracted services (data is not being sold or shared with third parties).

• Ask potential vendors if they support SSO/SAML2(link is external) and can integrate with CalNet (nice to have).

• Accessibility

• Ask potential vendors if their software meets the WCAG 2.0 level AA standards or if they have completed a VPAT.

• Ask potential vendors if they are willing to complete an Accessibility questionnaire(link is external) as part of a procurement process.

• Ask potential vendors if they are willing to participate in a hands-on accessibility review. Would they be willing to commit resources to address any major accessibility issues identified?

Check with the Web Access team(link is external) for guidance and tips for identifying an accessible solution. You can contact them via email: webaccess@berkeley.edu(link sends e-mail)