Looker is a BI application with an analytics-oriented application server that sits on top of relational data stores. It includes an end-user interface for exploring data, a reusable development paradigm for data discovery, and an API for supporting data in other systems.
N/A
ServiceNow IT Service Management
Score 8.6 out of 10
N/A
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.
As a Sales, it suited me to use such well-developed software with a nice dashboard that could navigate between my prospects, visualize the numbers of clients, and check my achievements for each quarter. That would help me understand my performance and record the data I needed for myself as a salesperson.
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.
Show visited pages - sessions, pageviews - which programs are viewed the most.
Displays session source/medium views to see where users are coming from.
It shows the video titles, URLs, and event counts so we can monitor the performance of our videos.
It gives a graphic face to the numbers, such as using bar charts, pie graphs, and other charts to show user trends or which channels are driving engagement.
Our clients like to see the top pages visited for a month.
I like the drop-and-drag approach, and building charts is a little easier than it was before.
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.
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!
I give it this rating because it deems as effective, I am able to complete majority of my tasks using this app. It is very helpful when analyzing the data provided and shown in the app and it's just overall a great app for Operational use, despite the small hiccups it has (live data).
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.
Looker is relatively easy to use, even as it is set up. The customers for the front-end only have issues with the initial setup for looker ml creations. Other "looks" are relatively easy to set up, depending on the ETL and the data which is coming into Looker on a regular basis.
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.
Somehow resources heavy, both on server and client. I recommned at least 50Mbs data rate and high performance desktop comouter to be abke to run comolex tasks and configure larger amount of data. On the other hand, the client does not need to worry when viewing, the performance is usually ok
Never had to work with support for issues. Any questions we had, they would respond promptly and clearly. The one-time setup was easy, by reading documentation. If the feature is not supported, they will add a feature request. In this case, LDAP support was requested over OKTA. They are looking into it.
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.
Looker gives you options to integrate external APIs with great ease. Our data analytics team is able to easily use multiple data sources as input to the Looker dashboard, and everything is consolidated in one single Dashboard. You also have an option for Shared folders to be accessed by multiple people. The reporting system is perfect and has a wide range of options/reporting options that can be implemented.
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.
Looker has a poignant impact on our business's ROI objectives. As an advertising exchange we have specific goals for daily requests and fill, and having premade Looks to monitor this is an integral piece of our operational capability
To facilitate an efficient monthly billing cycle in our organization, Looker is essential to track estimated revenue and impression delivery by publisher. Without the Looks we have set up, we would spend considerably more time and effort segmenting revenue by vertical.
Looker's unique value proposition is making analytical tools more digestible to people without conventional analytical experience. Other competing tools like Tableau require considerably more training and context to successfully use, and the ability to easily plot different visualizations is one of its greatest selling points.
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.
