Entrinsik Informer is a web-based reporting and business intelligence application popular in the higher education vertical market. It helps organizations transform real-time data into actionable information by delivering ad-hoc reporting, data analysis, and interactive dashboards.
N/A
Looker
Score 8.2 out of 10
N/A
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.
I think working on Looker could be hard, but in performance, it can easily overtake Wave and Zoho Reports. The flexibility of the system and it being super fast makes Looker a standalone from other similar software.
It makes creating queries very easy for end users so not only research or technicians can do it. The availability for creating Live reports that are accessible via Excel on the network has given many of our users the ability to get the information they need in a format they can use without needing someone to translate the raw data
Quick dashboards from Google Sheets - Easier to do the graphs than in Google Sheets - Operational dashboards to be used in the day-to-day work - It is good both for retrospective data and to do a pulse check of the current status - Better for not giant amounts of data and not multiple data sources. - If you need a lot of graphs to be displayed on the same page, it can be a bit glitchy during configuration (then the use works fine).
Simple user-interface: Informer is relatively easy to learn and end users can begin running reports and creating new reports quickly.
Email "burst" functionality: This feature allows emails to be sent out based on data in the report. So for example, a report could be scheduled that would email all student employment managers listing out the specific employees that report to them that haven't submitted their time sheets. Each manager would only see the rows that correspond to their email address.
Analytics and grouping: Users can quickly drag columns to group and sub-total, and can use the analytics tab to get deeper insights into the data.
Filtering - you can filter across different dimensions and metrics to get a more specific "cut" of data
Refreshing - data automatically ingests into Looker which allows reports to be updated and backfilled in real time
Conditional Reporting - you can leverage Looker's reporting features to flag when a given metric or KPI falls below or above a specified threshold. For example, if you had a daily sales benchmark in a SAAS organization, you could use Looker to flag whenever daily sales falls above or below the benchmark
There are a lot of reports that we have in Informer that say they have never been run, even though I know they have been run. So that makes it really difficult to determine which reports can be deleted to keep a tidy report list.
The only other complaint I have about Informer is that there doesn't seem to be a properly detailed error code/message when the student information system can't be accessed. For example, I am currently trying to move Informer to its own standalone server and I get an error message saying that our license isn't valid. Informer Support sent a new license, which prompted the same message, and the only explanation they have given me is that Informer can't reach the student information system. I would think that if that were the case, the error message would say that instead of an invalid license.
Looker is less graphical or pictorial which makes it less attractive
Consumes a lot of memory when there are multiple rows and columns, impacts performance too
At times when we download huge chunks of raw data from Looker dashbords, the time taken to prepare the file is enormous - The user fails to understand if Looker has frozen or if the data is getting prepared in the background for downloading. In turn, user ends up triggering multiple downloads
Informer has been handily meeting most of our reporting needs, and we've created a library of hundreds of reports that are used every day. They have a terrific support service to help when you have questions, and I've found them to be great at listening to what customers would like and adding new features. They are a small company that really listens and really cares, and I've been very pleased over the past few years getting to know them.
We've been very happy with Looker so far, and all teams in the organization are starting to see its value, and use it on a frequent basis. It has quickly become our accessible "source of truth" for all data/metrics.
From the perspective of the new user and a seasoned user I would say eight would represent both parties. It presents a 'familiar' interface and easy to navigate display. Tagging is quite nice and allows for organization of reports based on those tags. These have to be monitored like anything else to keep them consistent but provides a better than average means of organizing reports.
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.
I would have given 10 but no one and no system is perfect. The only issue with support is not the staff nor the response but the support Wiki and support pages in general run very slow at times. I believe this has been addressed by the company but the technical speed of the pages have been an issue.
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.
We bought the product on a Thursday morning, and we were writing reports on Friday afternoon. We did take about a month to manage the Mapping, Linking and Security to allow us to open it up across campus. We are now mapping from as many third-party vendors as we can to enable the creation of more ad-hoc reporting.
I have experience with Advizor AnalystX, and it was just awful. It is advertised as an interactive reporting tool, in which you can use your mouse to select and segment constituents by where they live (by clicking on a map), how much they've given to your institution, when they last gave, etc. In practice, their map feature was unusable; it's a static map image (imagine a paper map hung on your wall), rather than draggable and zoomable Google Maps, and it required hours of work to configure one map region. As far as computing constituents' giving statistics, it required way too much back-end work to build simple giving totals.
Looker is an off-the-shelf, free tool for Google business users. Other than the internal cost of time to build, we had no costs to set up what we needed to do. Knowledge sharing internally and using templates greatly reduced this cost, making the overall cost very low.
We have definitely improved customer service due to better reporting using Informer. All departments are better empowered to help our students in a more timely and accurate manner.
Using Informer has given us the ability to eliminate functionality within our ERP system and offload reporting to a data store instead of the transactional system. This has resulted in successfully upgrading our core systems and improved response times.
Allowing others to self-serve their own analytics and connect it to Looker simply and easily has helped unblock the central data team so they can instead focus on validated dashboards whilst stakeholders manage their day-to-day analysis themselves. Countless engineering hours have been freed up by not having to manage every user permission for each BI tool; we have a BYOBI approach; Bring Your Own BI
Creation and management of a semantic layer (LookML =Looker Modeling Language ) allows peoples sandboxes and production databases to become clutter free. Minor adjustments, conditional fields, and even some modelling can all be done in LookML which doesn't need oversight or governance from the central data team.
LookML, specifying drilldown fields and their sub-queries, as well as generally creating dynamic parameters with Liquid are all great features, but can have a steep learning curve. it may take some time to understand how to create this middle layer correctly, or even pose a risk of inheriting complex code from another source which can be unmaintainable if it becomes too big. Some level of governance is recommended if Looker is used by a large number of editors.
