Team Dynamix Glossary Flashcards
(130 cards)
1
Q
Account Attribute Sections
A
A section used to organize Account Attributes into one section, likely because the attributes are related in some form.
2
Q
Account Attributes
A
A version of Custom Attributes specific to Acct/Depts
3
Q
Acct/Dept
A
The Acct/Dept field represents the Department for which the project is being requested.
4
Q
Announcement
A
Project wide communications to the project resources, stakeholders, and/or contacts.
5
Q
Application Menu
A
The route to opening applications in TDNext, often referred to as “the waffle”.
6
Q
Article
A
A singular entry within the Knowledge Base.
7
Q
Article Owner
A
The individual who manages a Knowledge Base article and is notified of feedback (depending on the Notify Owner of Feedback setting).
8
Q
Articles Awaiting Review
A
Articles that have been submitted to the Knowledge Base that are in need of review to be Approved and Published.
9
Q
Asset
A
Hardware, software, or consumable within an environment. Assets of a service provider include anything that could contribute to the delivery of a service.
10
Q
Asset Attributes
A
A version of Custom Attributes specific to Assets
11
Q
Assets/CI
A
Allows users to easily add and categorize assets, configuration items, vendors, contracts, and locations allowing an institution to track and maintain hardware and software assets, in addition to other configuration items, cost-effectively.
12
Q
Blackout Windows
A
Times during which changes cannot be scheduled or performed
13
Q
Briefcase
A
Repository of files related to the project, organized into folders.
14
Q
Client
A
A user whom can authenticate to TDClient and access areas such as the Service Catalog, Knowledge Base, and their requests.
15
Q
Community
A
TeamDynamix centric website where clients can:
-connect with one another
-discover helpful industry content
-access downloads, articles, webinars and discussion forums
16
Q
Configuration Item Attributes
A
A version of Custom Attributes specific to Configuration Items/Assets.
17
Q
Configuration Items
A
Components of an infrastructure that currently is, or soon will be underconfigurationmanagement. CIs include both Assets of the environment and Services that are provided.
18
Q
Contact
A
Contact information record (name, phone, email…) of an individual.
Nothing can be associated to a Contact nor can they authenticate to the environment.
19
Q
Contacts
A
A TDX term use to describe the group of people associated with a given ticket.
20
Q
Contract Attributes
A
A version of Custom Attributes specific to Contracts
21
Q
Contracts
A
Documentation of the contract or warranty that is provided for an asset.
22
Q
Creator
A
The individual whom created the request. Depending on the point of entry it is possible for the requestor to also be the creator.
23
Q
Custom Attributes
A
Custom attributes provide you the ability to create fields for data capture
24
Q
Customer
A
A TDX term use to describe a People record for a requestor. A customer can be staff, faculty, student, affiliate, IT Pro, or not affiliated with the university.
25
Description
The full details of a request, including any appropriate circumstances or supplementary information that may aid in completing it.
26
Desktop
A collection of delivered modules and custom reports to give a snapshot view of current activity in the environment.
27
Evaluator
The individual person to review, process, and analyze the project request.
28
Event
An activity that occurs within a specific project on a certain time and date, this is much like a calendar entry.
29
Expense Account (Expense Type)
The classification of an expense entry, this can range from very high level (i.e, hotel expense) to a very granular configuration (i.e., Holiday Inn Expense).
30
Feed
An audit trail, with time and date, of all activity on the entry (ticket, project, issue, etc.). The Feed also supports comments to communicate with resources on the entry.
31
File Cabinet
Allows users to post and access project knowledge cataloged in the File Cabinet database. Users may search the File Cabinet according to custom file classifications as defined by your institution. In addition to posting and accessing data, the dashboard gives users a profile of user activity within the File Cabinet.
32
File Cabinet Attributes
A version of Custom Attributes specific to the File Cabinet
33
Finance
Generate invoices based upon billable time and expenses tracked in Time & Expenses. The Finance application allows managers to create invoices and integrate them with an accounting system.
34
Functional Roles
define the primary and secondary job duties that a user performs. After defining a set of Functional Roles, users will need to be assigned these values as this will help project managers assign users to projects based on his or her capabilities.
35
Groups
A collection of users
Groups serve the purpose of assigning responsibility, content sharing, and content visibility/permissions.
36
ID
Unique identifier of an item that is a numeric ID, i.e. “12345.” This number does not change as modifications are made to the item.
37
Impact
A factor in on determining the priority of a ticket. It is the measure of the effect of an incident on business processes. Criteria to calculate impact include, amount of potential financial losses and amount of affected users.
38
Industries
Industries are tied to accounts to help distinguish between types of Acct/Dept. Also used for to form a grouping of Acct/Dept, for example by institution division.
39
Issue
Issues are problems, gaps, inconsistencies, or conflicts that occur unexpectedly in the lifecycle of a project.
40
Issue Attribute
A version of Custom Attributes specific to project issues
41
Knowledge Base
The Knowledge Base is the TeamDynamix solution for Knowledge Management. According to ITIL Knowledge Management aims to gather, analyze, store, and share knowledge and information within an organization. The primary purpose of Knowledge Management is to improve efficiency by reducing the need to rediscover knowledge.
42
Knowledge Base Category
In the Knowledge Base, a category is a grouping that organizes articles.
43
Licensed User
A licensed user refers to a TeamDynamix user whom has a paid license associated to their account. These users can access TDNext.
44
Location
Reference to a place, often a building, where an incident or asset is located.
45
Location Room
The reference to the specific room within a Location of which is where an incident or asset is located.
46
Long Description
A comprehensive description of a service.
47
Maintenance Schedules
Period of time designated in advance by the technical staff, during which preventive maintenance that could cause disruption of service, may be performed.
48
My Accomplishments
Section within My Work application that lists the authenticated user's completed tasks, tickets, and issues.
49
My Approvals
Section within My Work application that lists approvals for resource requests, time reports, project requests, and service requests assigned to the authenticated user.
50
My Articles
An area within Knowledge Base dedicated to all articles the authenticated used is the owner of.
51
My Assignments
Section within My Work application that lists what has been assigned to the authenticated user.
52
My Schedule
Section within My Work application that lists the hours the authenticated user is scheduled for on a project or workspace.
53
My Work
A comprehensive application built for TeamDynamix licensed users. Users can easily see the tickets, tasks and issues to which they are assigned, make updates, track time, manage projects (when applicable) and access briefcase files.
54
News
A page on the Client Portal to display desired RSS feeds.
55
Order
A means to sort the entry by order value when displayed.
56
People
A TDX term used to describe the People Application, which allows for the creation and modification of all People records (including those who are not necessarily licensed users) as part of a database that can be used for the purposes of Asset Management and Service Desk Tickets.
57
Person Attribute
A version of Custom Attributes specific to People Records
58
Primary Manager
A project can have two managers, Primary Manager and Alternate Manager. The Primary Manager has ability to change the project manager while the Alternate Manager cannot perform that function.
59
Primary Responsibility
The person or group that is listed as responsible for the completion of the ticket.
60
Priority
Based on impact and urgency, and is used to identify required times for actions to be taken
61
Portfolio Planning
Manage project requests through request workflows additionally analyze project requests alongside other requests and existing projects to allow for planning and what-if scenarios.
62
Portfolios
Allows users to manage and view portfolios.
63
Product Model Attributes
A version of Custom Attributes specific to Asset Product Models
64
Product Models
A listing of the specific model of an Asset.
65
Product Types
Classify Asset product models into types such as “Laptop”
66
Project Attribute
A version of Custom Attributes specific to People Records
67
Project Attribute Sections
A section used to organize Project Attributes into one section, likely because the attributes are related in some form.
68
Project Name
The project name is the title to identify this project
69
Project Requests
Allows users to submit project requests into the Portfolio Planning application from Client Portal.
70
Project Request Status: Approved
Request has completed the project request workflow and is waiting staff the request and graduate to a project.
71
Project Request Status: Declined
This project request was declined i.e. it will not be moving forward.
72
Project Request Status: Not Submitted
Still waiting on the requestor to complete the request. Or, the request was returned to the requestor, perhaps for more information.
73
Project Request Status: Other Status
The status is the same as the name given to the current workflow step.
74
Project Request Status: Submitted
Request has been submitted, however it is not yet assigned a project request workflow for review.
75
Project Templates
Predefined elements (briefcase, contacts, issues, links, and plans) that can be applied to an existing project. Allows users to create templates for projects, including briefcase files, contacts, issues, links, and project plans, which can then be applied to new or in flight projects.
76
Project Type
A project type is a main (and required) component of a project and is meant to classify the nature of the project.
77
Project Type Categories
Used for organization and for reporting (if desired), it is a grouping of alike Project Types.
78
Projects/Workspaces
The Projects/Workspaces application allows individuals to be members of projects and/or workspaces. TDNext users also receive access to the Plan Manager for project plan build out, as well as management capabilities and reporting at the project level.
79
Questions
Much like a web forum, Questions enable users to share knowledge and/or ask questions of other users.
80
Related Articles
Relationships to other Knowledge Base articles that display when users view the article.
81
Related Processes
Identify which processes would be impacted if this project were to occur.
82
Relationship Types
A descriptor of the type of relationship between two Assets. Each Relationship Type also has an 'reverse description', for example "Is powered by" and "powers".
83
Request Form
The custom form associated with a service that the requestor will complete on the Client Portal.
84
Requestor
The individual that is asking for service to be preformed.
85
Resource
A user whom is added as a member of a project to add value by completing tasks and/or managing the project
86
Resource Management
Allows users to review and manage resource requests and overall resource allocation.
87
Resource Pools
typically classified by functional area or by the Resource Management area responsible for assigning resources to projects
88
Response Template
Used to populate the comments field when updating the status of a ticket
89
Response Template Categories
Used for organization within a ticketing application, it is a grouping of like Response Templates.
90
Responsible Group
The group of users that is primarily responsible for the completion of a ticket.
91
Reviewer
An user who can be notified when a ticket comes in, however not made responsible of the ticket. Tickets that one is the reviewer for can be found in the "Awaiting My Review" section in a ticket application.
92
Role Forecasts
Identify the skill sets and amount of estimated hours needed to achieve a project. A named human resource will not be assigned until the project request has graduated to a project.
93
Score Card
To accurately assess multiple project requests compare them against the same metrics. The score card will generate a score for the project request committee to utilize in prioritizing projects.
94
Service
The specific offering or activity performed that achieves outcomes for the customer without the ownership of the costs and risks. Services in TeamDynamix all reside in the Service Catalog on the Client Portal.
95
Services
The Services/Requests application allows individuals to browse the contents of the Service Catalog. It is the application which encompasses both the Ticket Requests and Project Requests applications.
96
Service Catalog
The TeamDynamix Service Catalog is one of the primary foundational configuration areas of the application. As you've undoubtedly heard by now, the formal definition of a Service (according to ITIL) is "a means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks."
97
Service Catalog Category
In the Service Catalog, a category is a grouping that organizes services.
98
Service Level Agreement (SLA)
Contract between a service provider (either internal or external) and the client that defines the level of service expected from the service provider. Configured to achieve Respond By and Resolve By metrics in defined time amounts.
99
Service Level Agreements
contract between a service provider (either internal or external) and the end user that defines the level of service expected from the service provider.
100
Service Manager
The individual or group who is primarily responsible for maintaining and updating this service as appropriate.
101
Short Description
An abbreviated description of the service, limited to 1000 characters. It is seen in grey text under the service name when browsing the service catalog.
102
Source
An indication of where the ticket request is coming form. i.e. client portal, phone call, etc.
103
Sponsor
A key resource that assist with project matters such as funding, scope clarification, progress monitoring and assumes responsibility for the request.
104
Standard Reports
Found in many of the applications, most notably Analysis, these are delivered/out-of-the-box TeamDynamix reports.
105
Status
Represents the state the entity (ticket, project, issue, etc.) is in.
106
Survey
A questionnaire to be sent to the requestor following the completion of a project or ticket.
107
Systems Affected
Identify which systems would be impacted if this project were to occur.
108
Tags
Labels attached to a service, article, or ticket for the means of identification or improving search results.
109
Task Template
Predefined list of tasks, that are in order and may include predecessors, that can applied to an existing ticket.
110
TDAdmin
Administrative setup interface used to configure TeamDynamix.
111
TDClient
Client/end-user interface accessible by all users.
112
TDMobile
An interface designed for devices that cannot access TDClient or TDNext. It provides basic and responsive access to some parts of TeamDynamix.
113
TDNext
TDNext is the foundational application suite upon which most other TeamDynamix applications run, allowing executives, project managers and project team members to work more effectively and report on data.
114
Tickets
Ticketing applications allow users to track transactions about services an area provides. Chose to track tickets of each classification (incident, problem, change, release, or service request).
115
Ticket Classification
The indication of the kind of ticket event. There are six Ticket Classifications: Incident, Major Incident, Problem, Change, Release, and Service Request.
116
Ticket ID
Unique identifier of that is a numeric ID, i.e. “12345.” This number does not change even if the ticket classification changes.
117
Ticket Requests
Allows users to submit ticket requests in to a Ticketing Application from the Client Portal.
118
Ticket Type
The type field is used to identify the nature of the work being done on a ticket.
119
Ticket Type Categories
Used for organization and for reporting (if desired), it is a grouping of alike Ticket Types.
120
Tickets Attributes
A version of Custom Attributes specific to a Tickets Application
121
Time Account (Time Type)
The classification of a time entry, this can range from very high level (i.e., ticket time) to a very granular configuration (i.e., research expenses, hotel expenses).
122
Time & Expenses
Time & Expenses is the route to account for users’ time and expenses on tickets and/or projects. Time & Expenses allows for manager approval or rejection of user submitted time and expense entries.
123
Title
A short description or name to explain the nature of the request.
124
Update
Action to fill in the current condition of the ticket, project, or issue in TeamDynamix. i.e. Update the status
125
Updateable
An option on a custom attribute that will present the attribute on the Update window when updating a ticket, project, or issue status.
126
Urgency
A factor in on determining the priority of a ticket. The time it takes to an incident to have a significant impact on business.
127
User
A people record who in which can authenticate in to the environment, depending on the level of access a user can access TDNext and/or TDClient
128
Vendor Attributes
A version of Custom Attributes specific to Vendors
129
Vendors
The business that serves as the Manufacturer, Supplier, or Contract Provider of an Asset
130
Workspace
A collaborative space that provides the ability to track initiatives that are similar but not quite a project. Workspaces can have resources assigned and scheduled, time can be tracked against them, and they can even have specific ticket types associated with them.
