The ibi™ WebFOCUS® product is an enterprise business intelligence and analytics solution equipped with data management, visual discovery, predictive analytics, and visualizations. Combining these capabilities and data science in one unified containerized platform, the WebFOCUS® solution can be used to make data-driven decisions across the enterprise and provide reports, dashboards, and customer-facing applications at scale.
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 would less recommend it because it looks like IBI is receding a bit from the European market. I would not be certain for future support. Knowledge in the market in western Europe is limited Functional wise the application suits almost all situations. I would for sure recommend it purely based on its capabilities
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).
One thing that has always been good at WebFOCUS is how they interact with the customer on items. They take suggestions and implement them. In addition technical support is timely and very detailed.
I think they keep up with and lead in implementing new technologies in the BI space. One case of this are the ability for user to create their own easy dashboard using the green plus buttons. Also the ability to link d3 into and have the ability to implement new types of graphs is nice.
I have been to a spoke at one of their user conferences and they are worth going to. In addition to all of the great seminars the interaction you get with vendors and other users is key in the growth of your knowledge. I've learned so much for my time at these conferences.
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
The newest versions of WebFOCUS have an unnecessarily complicated security layout that makes configuration difficult to accomplish without bringing in the vendor for installs.
This software tries to cover too many bases allowing you to switch from writing code manually to creating reports using only GUI tools. This sometimes complicates screens and functionality where the two methods don't always work well together. -though its nice to have the choice.
The sales force is not as top notch as many software companies
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
This software is deeply engrained with my organization and has become a tool that would not easily be replaced without spending more money and resources to get the same results. License cost is comparable to other report writing tools and the capabilities are greater than the competition without having to buy multiple apps to do the same thing.
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.
Best BI tool/product I have used. The others don't compare overall. Some can look fancier, but when you actually use them with large data and data from numerous systems/sources that is where most of the competition falls away. I also don't like downtime. I have basically none for a large user base with WebFocus. Even SAP Crystal Reports went down for 4 days once - 4 days because the admin password got locked out due to a glitch and we had zero reports for 4 days. WebFocus has never had more than a few minutes of downtime. It's like a tank that just keeps rolling. There is no other choice for reliable BI.
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.
They have extremely knowledgeable techs that I have worked with over the years. Some have actually become really good friends of mine. I see them often at local user groups and when we show them how we are using their tools to save millions of dollars throughout the company
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.
Plan ahead on what data will be accessible and the type of security required on the database and if you will want to use security that is built into the software. It is worth consulting with the vendor on what your plan is and how they recommend you proceed in order to get results you are happy with.
Webfocus handles the side of our business that is involved with our catalogs. Our catalogs is a huge revenue driver for us and this tool has been extremely useful with planning feature catalogs. Tableau is used more for marketing and merchandising purchases since we can filter data based on website sales.
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 are not yet a success story. Though we've been implementing WebFOCUS for over a year, we have very few products in our Production portal. Of course, this is not all the responsibility of Information Builders, but we were ill-advised by our 'training coordinator' in our training of staff and coming up to speed with the tools has been very slow.
Once skilled analysts and professional IT staff achieve a grasp of the products, they are able to very quickly create polished and well-received products.
The DW/BI project has helped us to establish standards and protocols of communication that will allow us to more quickly meet knowledge transfer requirements
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.
