Functional Design (Slate+SPS)

Executive Summary

The purpose of this document is to detail the functional design of the tools that will be used to facilitate the Slate+SPS Platform that will be deployed with this project.  It will be supplemented with a more detailed Technical Design that covers the specifics of the application elements that will comprise the overall toolchain.

Functional Components

The following sections will detail the functional components that are required to successfully implement this project.

Data Management

Purpose

In order to facilitate all of the functionality required of the Slate+SPS implementation, import formats, protocols and processes will need to be created to allow the management of the contact data that is not already part of the existing contacts sourced from upstream systems of record such as SIS, PAC, and other Slate instances. Any data sources that have not been integrated to standardize contact information across all Slate instances will also be within the scope of this project.

Functional Requirements

The following functional requirements must be delivered for a successful implementation of this application component:

• Existing Data
  • Slate+Advising (all students, current and former)
  • Slate+Alumni (all alumni)
    • Blended with Athena and curated by Alumni Relations team
• Incoming Data
  • Automated import of all required fields from the following systems
    • Slate+Admissions (for prospects)
    • Slate+Academics (for faculty)
  • Manual import formats and documentation for importing data not included in integrated systems
    • Communications curated contact lists
    • Career Design curated contact lists

Security & Access Management

Purpose

Given the sensitive nature of some student data, and the limits on who should be able to access these records, it is critical that the security model tightly controls who can access records based on their business needs.

Functional Requirements

The following functional requirements must be delivered for a successful implementation of this application component:

• For Leadership and cross-functional stakeholders
  • Allow access to all relevant records, workflows, and templates based on organizational role
• For Staff
  • Allow access to all relevant records, workflows, and templates based on organizational role

Communications & Outreach

Purpose

The Communications team needs to be able to effectively communicate with all of their contacts as part of their responsibilities.

Functional Requirements

The following functional requirements must be delivered for a successful implementation of this application component:

• For Admin Staff
  • Create/Review/Update/Delete email communication templates for commonly distributed messages
    • Types of comms here...
  • Send ad-hoc communications via email as required
  • A set of standard templates will be required for the most common types of communications to be sent
    • The extent of these templates will be defined more clearly in the technical requirements