menu
IT Learns Why a Manufacturer's Sales Team Waits "Forever" for Siebel Transactions « US English

IT Learns Why a Manufacturer's Sales Team Waits "Forever" for Siebel Transactions

SHARE ON:

One of my large manufacturing customers deployed Siebel CRM to dozens of remotely located sales and distribution centers to process daily orders, transactions, charges, and shipments. For months, the sales team complained about their experience using Siebel for these processes. For example, the sales team reported that the Search Account business activity “looked like it was done, but was just taking forever to show up.”

The manufacturing company had centralized resources for their IT Service Desk, networking, and application infrastructure teams, with no on-site IT resources in the sales and distribution centers. IT spent countless hours reviewing application and network system logs and diving into the backend infrastructure systems to identify the cause of the Siebel problem. They found nothing to explain it. In addition, since only the most frustrated users contacted IT, they lacked a true understanding of the extent of the problem.

Aternity Sheds Light on Desktops as the Source of the Problem

After months of no progress resolving users’ complaints, IT implemented Aternity Workforce APM. With Aternity’s business activity analytics , they were able to monitor several time-sensitive business activities for conformance to expected SLA targets. To investigate the cause of the slow Siebel business activities, IT used Aternity’s unique ability to capture the key-to-glass response time of any activity performed within any application.

As shown by the Activity Analysis dashboard below, Aternity breaks down overall response time into that contributed by the client and that contributed by the infrastructure. Armed with this information, IT came to three fast conclusions:

  • The slow activity was caused by the excessive time for Siebel to render on users’ screens, but the infrastructure processing time was very quick, across all servers.
  • Only users accessing the servers supporting the East Coast were feeling the pain.
  • Sales was the most impacted department.

 

 

Response Time for the slowest performing activities is broken down to Client side latency, and Infrastructure side latency

 

A quick confirmatory report showed a direct correlation between response time as the users are see it, and the local render time on their devices.

 

 

A direct correlation between the client time and render time is validated, and infrastructure response time is shown to be consistently quick

 

With the problem validated, IT was able to let the Network team off the hook. Why hadn’t the IT team previously identified the problem’s cause? They lacked the ability to look at the users’ devices, aside from a remote session here or there.

 

Confirming the Cause of High Desktop CPU

On the next user complaint, the Service Desk used Aternity to drill down to the user’s PC and confirmed that CPU Utilization was around 95% for about 40 minutes around the time of the complaint.

 

Quick drill down to a complaining user’s PC identifies a poorly scheduled Anti-Virus scan

 

A quick check of another user PC’s resource consumption from the same department revealed the cause – high CPU consumption due to an Anti-Virus scan scheduled for the middle of the day. A call to the central Anti-Virus solution owner within IT validated that during the last system upgrade almost 3 months before, someone accidentally set the schedule for the daily full scan from AM to PM. And as the Sales team was the first to receive the upgrade, they were the first to be impacted.

IT failed to find problems that were impacting a large portion of the Sales department, or even fully understand its scope because they were not monitoring those users’ PCs at any point in time. Optimizing the end user experience of business critical applications requires more than responding to user complaints. It requires understanding the end user experience of all users, on any device, across the entire enterprise. It requires setting baselines for expected performance so that deviations from those expectations can kick off a proactive approach to problem solving.

Resolution: A Proactive Approach to Problem Management

A targeted approach to reported problems is the bread and butter of every IT organization. IT frequently receives complaints from users, and investigates the problem based on reported symptoms. Spending time and money investigating in all the wrong places, simply due to the lack of visibility of where real problem may be.

If you’re experiencing problems similar to the one I’ve described, you can register for a free product evaluation of Aternity Workforce APM today.

top.name