Peter Beasley, President Netwatch Solutions
Many enterprises still enjoy success with legacy service desk solutions such as Footprints, Track-IT, and Remedy. Many DevOps and software driven enterprises use Jira effectively to manage their service desks. But these solutions, often perpetually licensed, may be customized to meet many internal business needs – but do not have the latest configuration management capabilities like predictive analytics, dependency mapping, gamification, auto-discovery and robust change management workflows. Many lack a CMDB (configuration management database).
So … wouldn’t it be great to have a CMDB without the hassle of changing your entire service desk functions?
Plus, most CMDB’s today require migrating from a fully amortized, perpetually licensed solution to a recurring, SAAS solution.
This session:
•Lists reasons to keep your legacy service desk
•Identifies key intersection points on how a traditional service desk can be complemented with a modern CMDB
•Points-out what deficiencies may hurt the most
•Emphasizes the plusses often out-weigh the negatives.
Keeping your legacy service desk may make sense for many enterprises when you find options to extend their capabilities. Learn how.