We've been able to get off of other platforms, resulting in a cost savings.

Also, the fact that we can monitor our customers' data performance and stay within our SLA means we don't have to send money back to them. If we don't meet our SLAs, we have to pay them back. SevOne provides us with a great cost savings there.

I don't think the product cost compares to the savings we get by detecting a problem and resolving a problem faster. We lose more money in an outage than what we spend on SevOne, so I think our return on investment is fairly obvious.

It is very difficult to put a figure on it when it is a support function.

One of the returns we get is an assurance, based on data, as to whether upgrades are necessary for our branches. For example, if one of the branches is complaining about throughput or anything else, then we have data to show them. In this way, we can decide whether an upgrade is really necessary, or not, which is of value to us.

We have definitely seen ROI from using SevOne. We've expanded our scope of control and we've increased the number of devices in our environment. Because we have different business units, we have a multi-tenant environment where devices are for different business units. Being able to organize them separately and increase the server count or the device counts has definitely helped us to provide some additional services.

We haven't actually measured ROI but in terms of the total cost of ownership, SevOne has certainly saved the company quite a bit of money. It's basically avoidance of paying high licenses with other suppliers is what we've saved. Our operations teams have a system that gives them the potential to give meantime to repair and it gives them the better ability in that area. We don't measure that so much. It's more about the savings we have from moving from one toolset to another. It's also operational efficiencies. I have five performance management tools and we can have one. People have got one place to go.

With respect to ROI, that 11 month period without a P1 or a P2 incident was the best return on investment I have seen as an operations manager. One does not make money with this product, but in terms of savings, you are not addressing P1s in the middle of the night because you saw that coming thanks to the performance data.

There is also time saved in terms of engaging with other teams. You can provide your data right upfront and data is often unassailable. This means that when a team comes to you saying, "Oh, your network is not performing.", you can pretty quickly put data in front of them either real-time on a screen, or in a PDF, or in any way that you want to deliver it and show them the data that says, "No, the network is performing. So, whatever your problem is, it is not here."

In terms of ROI, when we implement SevOne, issues and calls come in and there's the reduced cost of not having a person look at it because it does it automatically. When it does it automatically, you have a timeframe if the issue doesn't resolve automatically, at which point you may have to report to a person, "Okay, this application or these VMs or whatever are having problems right now." Then you have to take a look at it and see what happened. Sometime you can clear the logs and do all the other basic techniques like the other tools do. You manually clear the log and then you look at these things. Or you can create a policy and then the extra policy will come into place. Or sometimes the time doesn't match right or your timestamps changes and you'll face these kinds of problems.

We have definitely seen ROI using SevOne. For example, the tool has the ability to put the devices that we're monitoring into a maintenance state, which automatically puts the SevOne alerts into "snooze." We have customers that work with us during their maintenance, and they notify us to place their devices in maintenance states inside SevOne so that they don't get notifications. That has helped us to build better, continuous relationships. It's another opportunity for a relationship with our customers.

It also comes with out-of-the-box reports, and they help with time-to-value.
They serve as a proof of concept or a proof of configuration that we can use to design other reports. It's really great to have those examples, out-of-the-box. And we are able to quickly edit them.

I have seen ROI. 

We have definitely seen ROI. We are adding more value. This is the primary tool used, in terms of support. So, it does a really good job in terms of getting the data and our current use cases. It keeps us stabilized as well as up and running.

SevOne is definitely earning its money because different departments are requesting SevOne monitoring for certain situations. And it's extra-billing, of course. I never see any of it, I just see the devices and we add them and we charge them. So they're bringing in money. 

They're getting their money back.

I can't say anything specific about the investment in the solution because I'm not given that data by my company. But our clients are still using this solution after many years with our company. That is a good indicator that they must be getting a good return.

In terms of ROI, I don't have a whole lot in terms of metrics. However, I would say that with DI, someone has definitely started to come around from a visualization standpoint. Not only do you get an alert with an indicative color like red, orange, or yellow, but it is well represented for different stakeholders. It is not only useful for the engineer sitting at the desk but also for the tier-three that supports that engineer, all the way up to the vice president, who just wants to know how things are going.

They've come a long way in developing that. Back in the day, all people wanted was something that told them the status; red is bad, green is good, yellow means that you should look into it. That was all the information that they had. These days, people want predictive analysis and they want to be able to trend failure. They want to be able to dig into the numbers a little bit more and graphically represent that. To this end, DI is actually something that they're doing to chase that down and fill that void.

Historically, that hadn't been the case. I think DI came out approximately four years ago, and I think that's something that they're really doing to try and add value to the platform.

The ROI for my kind of business is difficult to assess, but if I could get rid of Tivoli, I'd reduce my load by two FTE’s which would give me a six month ROI as a back-of-the-envelope kind of guess.

We have increased our capability a hundred-fold over, so it was more of a customer performance thing than ROI. I could see stuff I never saw before. In our root-cause analysis, I would typically have eight level-six people and it could take 24 hours. That’s a lot of horsepower. Now it takes us a quarter of the time. That’s huge.

It's provided us with improvements in network monitoring and troubleshooting as well as advanced reporting solutions payback.

We have an ROI as our licensing price point is very reasonable. We're roughly five times the size we were when we first started using this product.

Fantastic – for money laid out vs. what you’re getting back, it's been great.

It analyzes events affecting the services we provide to our customers, and it helps to plan improvements that are reflected in customers satisfied with the services we provide , be clear at the executive level quality of services we are providing.

Our ROI is excellent. The product captures production issues and streams events to service teams who monitor our infrastructure. The product also provides pre-emptive production reporting so that any potential issues can be caught before causing a potential outage.

I work on the technical side and have no insight into ROI.