ServiceNow Review

Originally we rolled it out for ITSM because we were using different tools which weren't integrated.

Valuable Features

Originally when we first rolled out, it was obviously the fact that we had full IT service management in one area. We were extremely scattered and had many different tools all over the place and none of them were integrated. That was our initial sell feature for us.

As time has gone on and ServiceNow has evolved and matured, we are loving the ease of the product. Each year, each version, each release they come out with is all that much more configurable for us. One of the biggest things for us is the fact that we've had the opportunity to be a partner with them and have had the opportunity to have some input and feedback on their product to begin with and have seen some of that that have come to fruition. In fact, I just saw a demonstration and there were several things that I know were a part of suggesting and the input that they received from their customers.

Room for Improvement

I hadn't really thought much beyond the improvements that I'm seeing that they're putting out in Helsinki. My organization is currently on the Fuji release. We were going to be upgrading to the Geneva release in July. One of the things we were coming here [to Knowledge16] specifically to look at is jumping on the release and going straight from Fuji to Helsinki. Considering some of the things that I just saw that they rolled out, I'm going to be pushing pretty hard for that.

Many of the things that we felt needed a little bit more shoring up was their CMBD product and their discovery, they seem to have covered that in the Helsinki release. I'm not really thinking of what the next step is going to be at this point. I was wowed with Helsinki, so at this point I'm looking forward to rolling that in and working with it.

Use of Solution

We implemented it back in 2011.

Scalability Issues

I like the scalability of it. We need an instance that we will have it within 24 hours. In fact, we have several instances in the Cloud. We have our production instance, we have a test instance, and we have four development instances.

Customer Service and Technical Support

I'm not necessarily involved in the day to day support that we would have to reach out to. Our architect is more involved with that. However, I do know that I have been the contributor of a few of the bugs that have been found. They seem to be very responsive, work with our developer and our architect team and work through the issues.

Initial Setup

When we started out, we did it in phases. Our very first phase was the change management application in a very condensed version of the incident management application. Phase two rolled out in late 2014. At that point, we went to a full incident management application. We revamped our change management application, rolled out problem service catalog, discovery, our CMDB. We have quite a few, some 38, applications that are currently turned on. They were pretty basic and we've been over the years developing and expanding those.

**Disclosure: My company has a business relationship with this vendor other than being a customer: We're partners
More ServiceNow reviews from users
...who work at a Financial Services Firm
...who compared it with Fujitsu RunMyProcess
Add a Comment