This global software company was struggling to manage licenses across nine different systems from recent acquisitions. This caused delays, errors and a poor customer experience. They implemented SafeNet's Sentinel EMS to streamline licensing which integrated easily and automated processes. This centralized management of licenses, reduced support calls by 48% and enabled faster order fulfillment and a better customer experience.
To Graph or Not to Graph Knowledge Graph Architectures and LLMs
EMS Case Study
1. CEO, CIO, Operations, Engineering,
Sales and Customer Support team
up with SafeNet to streamline and
automate the licensing of their
software products.
CASE STUDY
Sentinel EMS easily integrated into company systems, enhancing existing workflows without having to redesign or change
any existing mission critical components.
Background
This global leader in enterprise resource planning software and Challenge
services provides ERP, CRM, HR, Financial and Supply- Chain • Rapid Delivery - Unify and automate the licensing of software
Management software specifically tailored to a number of products
industries such as healthcare, finance, banking, manufacturing and • Scalability - Ensure operational systems can handle the
government. Their suite of innovative software provides end-user licensing needs of new products and can deliver licenses in
tools for overcoming strategic obstacles specific to their sector and the most efficient manner to end users and partners
has taken years to build and perfect. • Reporting - Gain customer insight and better utilize up-selling
As their product portfolio continued to grow, supporting the various and cross-selling market opportunities
licensing systems and processes was becoming unmanageable. • Efficiency - Minimize the headcount needed to support licensing
They required a robust solution that could streamline all of their
proprietary systems. This universal system needed to seamlessly
integrate with their back-office systems to enable complete Solution
software license visibility across the organization. • SafeNet’s Sentinel EMS
The Business Challenge
With over 6,000 customers worldwide spread across 23 locations Results
they are an extremely successful organization. However, as their • Automated license registration with centralized portal
customer base continued to grow and product lines began to management significantly reduces errors and mistakes
multiply, the company began experiencing internal difficulties. • License generator-agnostic design centrally manages disparate
license systems with reduced integration complexity, cost
In a matter of three years they had acquired four companies. Each and time
new acquisition brought its own set of products, technologies and • Advanced data collection and reporting identifies new revenue
licensing models. According to their CEO, “These acquisitions really opportunities with flexible and easy-to-use tracking tools
allowed us to expand on and diversify our offering to better meet • Enables better internal communication and processes, faster
our customers’ needs, but it left us with nine different licensing turn around times and a much improved customer experience
systems for our engineering teams to maintain.”
EMS
Sentinel EMS Case Study 1
2. In fact, it was not just the Product Management and Engineering
teams that were suffering. These disparate licensing systems The Solution:
were affecting almost every department within the company, not The organization chose SafeNet Sentinel EMS, licensing
to mention the repercussions that were filtering down to their entitlement and management system, to streamline the back
customers. “My team could not even focus on our core business office licensing process. A few of their products were already
because 48% of incoming calls were support calls around license licensed using SafeNet enforcement technology, Sentinel RMS,
management,” said their VP of Customer Support. which further boosted confidence in their decision to move
forward with Sentinel EMS.
Customers were continually calling due to delayed fulfillments,
erroneous product orders, and overall confusion. Jumping through Sentinel EMS’s is built to be enforcement technology-agnostic
all of these hoops to onboard and support customers was expensive with existing hooks to support Sentinel RMS, but architected
and the cost was unjustifiable. Furthermore, the company was to support any type of licensing. Therefore, there was no
allocating all of these additional resources in vain, as the process development required for the product lines that were already
was just as clunky and painstaking for the end user. being supported by SafeNet. Integrating the other licensing
systems was fairly straightforward as well, since Sentinel EMS
It was clear that the current software solution was affecting
supports the implementation of plug-ins that can call other
everyone within the company. What was unclear was how to fix the
licensing solutions.
problem or which department should take on the responsibility. As
the Operations Director indicated, “The procedures required for With Sentinel EMS’ robust set of web services, integration
fulfilling a product and registering a customer were painful. In with existing back office systems allowed for streamlining and
some cases it took a month just to deliver our products to our automating the licensing process. Using SafeNet’s out-of-the-
customers. I was continually emphasizing to our IS folks that the box connectors minimized the effort required to integrate with
systems we had in place were outdated. Product lines needed to SAP and SalesForce.com. SafeNet’s Professional Services Group
be standardized.” provided implementation services to get them up and running
and training services to prepare their IT organization to support
The company’s CIO stated her perspective: “My team was
and maintain the solutions moving forward.
maintaining a mix of homegrown and third party licensing
systems which was only supposed to entail a small percentage
of their job requirements. Keeping them running was already
consuming the IT department, let alone allocating the time or
skills necessary for a complete overhaul.”
Simultaneously, the Sales team was reporting that customers were
complaining that they had not received their products or that the
software was not working at all. The Sales SVP said, “Our team was
already frustrated by the lack of customer visibility around our
products, which made it difficult to up-sell current customers—
but when new customers were calling because they were still
waiting to receive their software after a month, we were livid.
Time was now being allocated to assisting unhappy customers
instead of generating new accounts and revenue.”
Disparate systems were hindering internal communications and
resources and sucking time from a number of departments within
the organization. Furthermore, the current customer experience
was suffering and that dissatisfaction was trickling over into
prospective customers. Something had to change.
The Journey
From the beginning it was apparent that the organization would
not be building this new system internally. Moreover, even
with third party help, they were not looking forward to ripping
out current licensing. As the Head of Engineering put it, “The
implementation required recoding all of our products, which was
a huge commitment to make. And even after the implementation
was complete we were still responsible for supporting the old
licensing technology for current customers until they migrated to
the new system.”
Sentinel EMS Case Study 2