SAP BusinessObjects Business Intelligence vs. ServiceNow IT Service Management

As mentioned earlier reporting was a big headache for us and the tools we used didn't support large data sets and visualization Performing analytics with such data sets was cumbersome and later post using this SAP BusinessObjects Business Intelligence we were able to correlate different data sets and prepare the dashboard pretty easier which were helpful and easier to understand.

Incentivized

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.

• This software is easy to initially learn, and very powerful in producing reusable reports.
• It is much faster than my company's internal manual queries. The ability to build off of a saved query and share queries to other users is a great positive.
• My favorite part is that you can run queries in the background and it does not interfere with your current work or slow your computer down.

Incentivized

• 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.

Incentivized

• The installation can be very complex and time-consuming, it requires a lot of planning and foresight as to what role the software will play in the organization.
• The software has a relatively large learning curve that takes dedicated users months to get comfortable with, the UI is a bit intimidating for new users.
• SAP could organize their help better, it can be difficult to find dependable solutions to issues via their website and support channels.

Incentivized

• 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!

Incentivized

The institution has decided to move in a different direction, and will be using MSBI for reporting. I have been very happy with the Business Objects suite of tools, and will continue to use them heavily until we make the transition.

Incentivized

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.

From a server and client side perspective. the Business Intelligence Platform provides a foundation for all aspects of content development, distribution, analysis, collaboration and self service. Ease of use from targeted content delivery through controlled accessibility. Content exporting in the format of the users choice. Scheduling for internal or external delivery. Public and private folders for secure content access when requied. Web based for viewing on the users device of choice without the need to download additional applications.

Incentivized

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.

When we implemented 3.1, we had a tough time managing the system: It took almost a year to stabilize.

With 4.0, we want to roll out to more users, and are holding back because of fears about the performance issue

We have never had any issues with ServiceNow's availability that I am aware of in the two years I have been using it.

Incentivized

Overall, the tool (Web Intelligence 4.2) is fast and solid. One issue is a dependability on JAVA for a full feature report creation/edit capabilities (as opposed to limited HTML option). Second, planned end of JAVA support by major browsers (Chrome is already not supporting JAVA applet).

For a massive system, page loads are reasonably quick, including searches.

Incentivized

SAP has released various versions of SAP BO BI. starting from 3.1 and going to 4.0,4.1,4.2 and latest being 4.3. SAP provides support to these new versions. As new versions keep on coming, support for the very old software goes out of scope from SAP. it is when the different organization plans to get their BO content migrated from a lower version to a newer version. The newer version had definitely added functionality and features which ease the work of users.

Incentivized

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.

Incentivized

SAP authorized training is best, Please go ahead with it. Even lot of online training options/videos available for self learning

Incentivized

I haven't used it or got feedback from the end user.

Content looks to be pretty detailed. Focused on SQL but not BW.

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.

Hire specialists and experienced staff. Mix some beginners so that everyone is not a leader but a learner too. Plan well; architect well; break down implementation in small steps and move towards larger steps. Create a centralized and authorized SAP Business Objects implementation team.

Incentivized

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.

Incentivized

We selected SAP BusinessObjects Business Intelligence (BI) based on price. It can stack up against others in terms of price and honestly, that's about it. Salesforce Commerce does a hell of a better job at handling it. However, in the space of Business Intelligence, SAP can do more, and that's why at the end we went with it

Incentivized

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.

Incentivized

SAP BusinessObjects Business Intelligence (BI) Platform supports SOA Service Oriented Architecture. You can start/restart/enable/disable all the servers. You can seamless do load balancing and clustering. It supports all leading application and web server. Supports LDAP SSO integration. People who can work on excel with training they can work on SAP Business Objects Web Intelligence, dashboard, Lumira, Information design tool product suite. Tool is very user friendly and easy to learn and implement

Incentivized

ServiceNow works as an enterprise solution.

Incentivized

• By generating and distributing reports in a timely manner, we were able to save millions of dollars for the company which otherwise would not have been visible.
• Almost realtime dashboard, saved the company a huge amount by showing the outages and kept the company from buying a tool to do just that.
• It showed the customers who were not paying the bills and were missing in the system due to some loophole. This was visible by doing reporting on the theft usage of electricity.

Incentivized

• 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.

Incentivized