OpenText™ Solutions Business Manager, formerly from Micro Focus is enterprise-scale business process automation software. It helps IT quickly create, adapt, deploy, and govern process-based apps and workflows for humans and systems across the organization.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
I was involved with a migration from HP Service Manager to ServiceNow, and the difference between the two was quite obvious right away. ServiceNow offers more features, more integration, a more friendly user interface, the list goes on and on. Unfortunately this is the only …
The question for an enterprise IT department today is... do I choose:- BMC Remedy ITSM - ServiceNow - BMC RemedyforceYour unique needs, implementation partner options and organizational DNA will drive the decision.
HP Service Manager, IBM Tivoli, BMC Remedy, CA Unicenter. None of these tools provided the open usability and configuration possibilities that ServiceNow has. They also do not have the integration between all the processes to the extent that ServiceNow has.
How many users will be using the system? What part of the organization will own the product? Serena is a great workflow tool. It can be tailored to fit in any scenario and so I dont believe there is any situation where it would be inappropriate.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
One of my favorite capabilities within the Serena user interface is the reporting. Detailed searches into the workflows allow the users to create reports containing any field that is in the workflow. Users here use the reporting during review time to pull metrics on tickets they have worked during the year. From a process perspective, the system provides a specific report with details around how long the items have been in various states. I use this information to measure my process peformance and to identify bottlenecks within the processes themselves. The reports are fairly easy to use but they can also be very complex too. Reports can be set up and shared across groups. Generic reports can also be set up so that query at run time fields can be entered.
Developing new processes in Serena Business Manager is relatively easy and does not necessarily need to be done by a developer. Serena has added some key features that reduces the need to add Java scripts. Serena Business Manager is a blank slate and it can be as complex or as simple as you make it. The forms are the same. I have seen some very simple designs and some very complex and beautiful form designs.
From a user perspective, it is fairly simple to just pick up and start using. I introduce our new hires to the systems in a thirty minute session. Most users are more confused by which process to use for what than by how to use the system.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
Serena's documentation for the product is well written but it can be a bit challenging because it is often missing key components, best practices or tips and tricks that you get when you call into their customer support. It is also very frustrating to have their release notes refer back to their knowledge base to have their customers figure out what they fixed in their releases.
Serena Business Manager manages their users in an Administrator function. Any changes made in this part of Serena is only logged in the database. It would be nice to have some reporting out of of this system. When you have multiple administrators of a system, it would be a nice feature to have some reporting here rather than having to go into the database.
The notification feature within Serena can be a bit challenging and time consuming. You can't copy the notifications so if you want to duplicate a notification you had previously created you have to recreate it again. The notifications have three levels to them and they can be a bit tricky to get them to work just right.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
We have been using Serena for eight years and I don't believe I can answer this question since it was so long ago that we made the decision to purchase Serena.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
We use Serena to standardize our business processes to ensure a more efficient work day experience for our employees. By having the employees use Serena for the processes we can ensure the process is completed the same way every time.
By having our key processes in Serena we are able to measure our processes at any time. Some of those key metrics include a 90% reduction in rework and a 47% reduction in overall process time. With the ability to measure processes at any time, we can react to process problems and correct them quickly. Serena Business Manager is flexible enough to allow quick development and rapid promotion when necessary.
Serena is very ingrained in our culture and the culture has taken on the "ticket" mentality unfortunately. With everyone trying to measure their work and justify their body counts through ticket counts, having a ticket opened for every act of work has become the standard.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
