What is Technolutions Slate?  

Slate is a comprehensive, web-based platform developed exclusively for higher education business needs. Optimized for non-technical end users, “it provides a single, unified interface to CRM, outreach, and communications, travel management, online applications, online reading, student success and retention, and alumni and donor engagement,” per the Technolutions website.  

Currently there are five instances of Slate across Tufts; the Dental School and the MD program are the only entities without Slate engagement. Each instance was implemented with TTS assistance over 2014 and 2015, but ongoing maintenance, development, and customization have historically been left to each instance to manage on their own.  

Vision for TTS Support Model  

The TTS Slate Team will provide University clients with access to dedicated staff who are experts in the capabilities of Slate and who aim to:  

• Model responsible stewardship of University resources by promoting improved business processes and information sharing within and across Slate instances/graduate program offices.   

• Utilize Slate’s features to increase efficiency and improve user experience for internal and external constituencies.  

• Improve data integrity and standardization to facilitate University-wide data reporting and archiving while minimizing errors.  

• Ensure adherence to data security policies.  

Proposed TTS Service Areas  

System Enhancements and Optimizations 

The Slate Team will meet regularly with clients to identify needs; advise and educate on best practices and upgrades/new features available in Slate; build out moderate to high complexity business processes and support/train clients to build low complexity business processes.    

Bug Fixes and Emergency Assistance 

Upon request, the Slate Team will provide timely assistance with processes not performing as expected, functional questions, and support in escalating emergency performance issues to other TTS services and/or Technolutions support.   

Application Development and Support 

The Slate Team will develop and maintain all technical requirements/configurations for collecting applications (custom application builds, application integrations, periods and rounds, automations, etc). They will also oversee implementation of new features/upgrades as needed.   

Data Security and Integrity

 
The Slate Team will develop and maintain all technical configurations within Slate instances to ensure compliance with Tufts data security policies and integrity and accuracy of data that passes between Slate and other internal and external systems (TouchNet, SIS, DataWarehouse, etc.).  

Staff training

 
The Slate team will provide training to complement existing Technolutions resources specific to the Slate instances at Tufts. Introductory training for Slate will be available to all new hires.   

General Services 

The Slate team will also provide services such as business process consulting, coordination with technical stakeholders, facilitation of information sharing, and annual system maintenance.  

Client Responsibilities  

University Clients will designate a staff member to serve as the “Slate Captain” (or “super user”) for their instance who will:  

• be the main point-of-contact for the TTS Slate Team  

• be responsible for ensuring client-side compliance with end-user best practices   

• build, or advise other client staff on how to build, low complexity business processes in Slate (creating events, building reports/queries, etc.) utilizing guidance and libraries provided by the TTS Slate team as necessary  

• ensure the day-to-day functionality of their Slate instance (audit processes, importing documents, consolidating records, etc.)  

• maintain instance-specific process documentation  

• identify and elevate requests for system enhancements and optimizations  

• actively engage with the TTS Slate Team and other Slate Captains in trainings, information sharing, and other professional development activities related to Slate  

Notes and Open Questions  

• How do we generate buy-in for this model? This proposal would decrease access of current users, and they would be required to interact with TTS to build/create/enhance their instance in any way that could affect reporting, flows to other systems, data integrity, and security.   

• Potentially related, who pays for Slate?   

• This document was written based on experience with GradHlthSci (GSBS and NUTR), TUSMPD, Vet, and Fletcher instances, and the University College database. Currently we do not have visibility into ASEU and ASEG, and this document reflects that. What is the expectation of the involvement of the TTS Slate Team with ASEU and ASEG?   

• How do we get Slate into the discussion when we evaluate vendors with applications that meet specific business needs (Accommodate, Salesforce, Hubspot, Destiny 1, etc.)? Slate is highly customizable, quick to implement, and already has a user base across campus. What other places can Slate work for us?