TeamDynamix Basics

• Cornell has a licensing agreement for a single instance of TeamDynamix (TDX).
• Cornell’s instance of TDX is a private cloud instance.
  • We don’t share databases with other TDX customers.
• We also contract for the vanity domain name option.
• We have created tdx.cornell.edu in Cornell’s domain name service.
• TeamDynamix releases a new version twice a year, with smaller maintenance releases being released weekly.

What’s Inside a TeamDynamix Private Cloud

• System Administrator access is in TDAdmin.

• Support user (technician) access is in TDNext.
• Customer self-service access is in the Client Portal.
  • Portal users can be authenticated or unauthenticated.
• System-wide settings like Security Roles, Locations, People, and Departments.
• TDXApplications.

What’s a TeamDynamix Application

• An application is a separate “bucket” within TDX that can have its own purpose, forms, services, security permissions, ticket types, etc. It’s analogous to what we use Companies for in Remedy.

• There are three basic types of applications: Ticketing, Asset, and Client Portal.

• Ticketing can include service requests, incidents, major incidents, problems, changes, and releases – these are called ticket classifications.
• Multiple ticketing applications can link to the same asset application.
• Client Portal applications include a service catalog, knowledge base, and a place for customer to view and update their tickets.