TeamDynamix Implementation - Q&A

UMS:IT is in the process of implementing TeamDynamix for Service Management as well as Project & Portfolio Management.  This article provides answer to question that have been asked during this process and will be updated throughout the project. 

Visit the TeamDynamix Implementation Approach article for more information about the overall implementation and status. 

Detailed Information

Specifically, what existing UMS products (Jira Service Desk, Confluence, AssetTiger, assorted project management software) are being replaced/retired by TDX and its modules?

• TeamDynamix will be the primary service management tool for all of IT replacing:

  • Jira Service Desk
  • Jira
  • Confluence
  • AssetTiger (or any other asset application campuses may be using)
  • Smartsheets for Project Management
  • And miscellaneous Google Sheets, Google Docs, etc where the information better fits in TeamDynamix
• If specific needs are identified that can not be accomplished in TDX, every effort will be made to integrate with other tools so that TDX still represents the entire organization. 

Does the TDX ticketing system come included with our current pricing/TDX package?

• Our contract with TeamDynamix includes unlimited users and unlimited use of their tools that support:
  • Service Management:
    • Self-Service Portal
    • Asset & Configuration Management
    • Change Management
    • Incident, Request & Problem Management
    • Release Management
    • Service Level Management
    • Service Catalog
    • Ticketing
    • Ticketing Workflows
  • Project & Portfolio Management
    • Project Management
    • Project Request Management
    • Portfolio Management
    • Pipeline Management
    • Change Control
    • Resource Management
    • Risk Management
    • Time & Expense Predictions and Tracking
  • Our contract does NOT currently include iPaas - Integration Platform as a Service 

When will use of Confluence & Jira end?

• Atlassian has announced support for all on-premise instances of Confluence and Jira will end in February, 2024
• Given the resources needed to support those tools, as well as the potential security risks involved with running out-of-support applications, we will be planning to retire and decommission those applications at a yet to be determined, future date. The service delivery team that is responsible for maintaining the Atlassian applications will be heavily involved in planning its decommissioning. Part of this process will include a plan to archive essential data that is currently stored in these applications.

What about other departments that use Confluence & Jira Service Desk?

• TeamDynamix is licensed for potential deployment across the full UMS organization, not just IT.Project teams have already begun working with other departments such as HR and Procurement to evaluate their potential transition to TeamDynamix.

As a T3 team, will the new system cause us to interact more with customers?

• TeamDynamix in and of itself will not determine a team’s customer interactions. Decisions about processes made during the implementation may or may not impact this.