Summary
This article provides the timeline and implementation components departments need to consider and plan for when requesting implementation of TeamDynamix.
The ESM (TeamDynamix) is NOT APPROVED for collection or storage of sensitive data classified as: passwords, Family Educational Rights and Privacy Act (FERPA), Payment Card Industry (PCI), Personally Identifiable Information (PII), Protected Health Information (PHI), etc.
Implementation Timeline
- 4-8 Weeks (May vary due to needs and resource availability).
- No implementations can go-live in August, January or December.
Required Implementation Components
The TDx Administrator manages required components. After implementation the TDx Owner or a designee must submit a TeamDynamix Service Request to request changes.
| Component |
Details / Guidance |
|
|
Implementation Owner
|
Serves as the primary contact for coordinating the department’s implementation and ongoing use of TDx. Before go-live, the TDx Owner must confirm that all in-scope requirements have been completed.
|
|
|
Clients or Customers
|
Who are your clients/customer?
Students, Perspective Students, Alumni, Faculty/Staff, Public, etc.
|
|
|
Service Pages (Client Portal)
|
A service page briefly explains what a service provides, who it is for, and how to request it. The content should help requestors quickly determine whether the service meets their needs and identify the next steps. Do not treat the service page as a general webpage or include individual team members’ names or contact information.
Tips: Keep the content brief, review examples, and use Microsoft Copilot Chat AI to help draft the description. Always verify and revise AI-generated content.
|
Simple Syllabus Service Page |
| Ticketing Form (Client Portal) |
What information do you need to collect from clients who will be submitting tickets? Forms should not contain a large number of fields. Will any sensitive data be entered in form fields?
|
Ticketing Form Example |
|
Ticket Attachments
|
What if any attachments are expected with submitted requests? Will any of the attached files contain sensitive data?
|
|
|
Respond By SLA (Service Level Agreement)
|
A Respond By SLA is a timer that ensures requests (tickets) are responded to.This timer ONLY counts down during business hours. Reminders are sent based on thresholds you choose. For example, if an SLA is 4 hours with a 50% threshold, agents are reminded to respond after 2 hours.
SLAs typically range from 2 to 8 business hours.
|
|