Anonymous UserBusiness Analyst at a tech services company
Anonymous UserGeneral Manager Information Technology at a engineering company
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"This solution allows us to change our performance metrics and tracks our goals in real-time."
"The data certification feature, where the admin user can put a certified stamp on a data source so that other users can know that that is the correct and accurate data flow or data source to use, is a good feature."
"The ease of use, overall, is one of the valuable features, as is the ease of setup. Other than making sure IT was aware of, and agreed with our proceeding, we did not need IT for any of the setup. The ease of setup is more valuable than you might think. The ease of configuring the security policies, setting up groups, and setting up personalized data permissions so that only certain people can see certain data — that stuff is amazing... Domo really is extraordinarily full-featured, but it's really easy to use."
"Domo is not a difficult tool to learn. All you need to know is the SQL for the ETL part. You don't need to write much code. That's the great part. It uses legacy languages, like SQL, which is very common among developers who then don't have to go and learn Domo's own syntax. Therefore, you don't have to learn another hard language to use Domo."
"It has the best GUI. And it already has an ETL tool embedded in it..."
"With ETL transformations in SQL lists, you often write a lot of queries. You have to build a bunch of code for the data. With Domo, one of the pieces we have is Magic ETL. In Magic ETL, you don't need to write code. You don't need to be a specialist in SQL or any database query language."
"One feature which I have found to be very interesting is the Beast manager, where you can create calculated fields. They are shared in one common repository so someone else can use the same calculated fields; they don't have to rewrite or reinvent the APIs."
"In Workbench 5, they have come up with a very useful feature called Upsert. When you're pushing data into the data set, if the data is already available it will update the data, and if that the data is not there it will insert it. That is a beneficial feature that they introduced in the latest version."
"They are introducing AI. There are good forecasting features and machine learning."
"The most valuable feature is the ability to set up the automated delivery of reports."
"The solution is easy to use and very flexible."
"I like the architecture of this solution. RPV is a powerful feature in Oracle OBIEE. It lets us design as per the needs of the organization. I can have multiple presentation folders and presentation layers. I can have customization in a single node in VMware, which is a very good feature of Oracle OBIEE. It helps customers in designing as per their requirements."
"The visualization is very good."
"The most valuable features are the lexical parameters and distribution."
"The most valuable feature is the ability to run it in Exalytics within memory coupled to a Repository on Exadata is where it flies. So it's not meant for mom and pop shops, but if you are a global 500 fortune 1000 company, this is a tool that can get you what you need on time and even in real time."
"The most valuable feature is the user-friendly set of tools that the customer can use to develop their own business dashboards."
"I would like to see more dashboard creation options."
"I would like to see more flexibility in their pricing structure. The trend is moving from database pricing to a user-license pricing model. That would be a benefit if they wanted to reevaluate their pricing structure."
"The ETL way of storing is not up to mark. You have to rely on the naming convention that you're using in Domo because there are no folder systems where you can collate all your workflows and put them into separate folders. A folder system should be there so you can easily identify how you are working. Once you want to make some changes to your ETL, then you can see the whole lineage, identifying what is there and not there."
"The forecasting feature, the regression features, and the Python libraries could all be improved. They're all in beta."
"In Tableau, you can create virtually any kind of visualization. Based on your creativity, you can create a visualization on a human body structure, you can create a visualization on anything that you want. But Domo is limited to a few kinds of visualization views: standard things like bar, pie, and some other charts... I would like to see them add new views for presenting the data in the visualization space."
"It's too early for me to say that something needs improvement, but there are times when there have been some flexibility issues with Domo... Tableau has a window function which can be integrated into a calculated field. That is missing in Domo so you have to make changes to the data set using ETL or SQL."
"When you're exporting a graph out of Domo — suppose it is in the form of a donut chart or it is in form of a stack — the data comes out in tabular format, not as a graph. When exporting the data, I would like them to create a tab for graphs and another tab with the data in tabular format."
"The solution is too expensive for small firms."
"It takes a lot of maintenance to support the architecture, which is something that should be improved."
"The solution needs to be easier to scale."
"Even though we have a feature to enable the physical query to be seen in the log, in case of any issues, it is challenging to debug and see or identify where is the issue. For example, we designed the OBIEE repository and deployed it into the server, and we are now accessing and creating a report. For some reason, if the report is not working as expected, it is very difficult to identify the issue. We have a feature to see the physical query that is being generated in the central OBIEE server. I feel that this feature should have been available at the repository level so that while designing the repository, we can select the presentation columns and the query it is going to create. This will avoid the additional task of deploying a feature into the server and then testing the report. It will also make the implementation process friendly if, while designing the repository, we can see: How is a feature working? Are any of the presentation columns selected? How is the query being generated? Which query is being generated? Are any joints used? What kind of joints are used? Having this kind of information will make Oracle OBIEE more powerful and developer-friendly."
"The pricing model could be improved. Right now, it's quite confusing. Many customers have this feeling that it's a super-expensive option."
"It was a little bit tedious to install a new release."
"One significant improvement is the need for simplification. The set up could be more intuitive. An enterprise setup with HA and DR are pretty complex and to get a robust solution one has to play around with Real Application Cluster data sources and FAN notifications as well as WebLogic clustering and external load balancers. SSO also is not that simple to set up especially if you want all your Oracle systems to use the same SSO solution, i.e., no cheating with direct LDAP connectivity."
"The complexity of this product means that you need to have a technical team to develop the reports, although this is also true for products like Microsoft BI and Zoho."
"For about 100 users our cost is $95,800."
"Because it's software as a service, it's more expensive on the face of it. But there are a lot of variables. I don't have to pay for servers or for infrastructure. I don't have to pay labor for my IT organization to set up or maintain the environment. I don't have to pay for them to upgrade the software, and test it, etc., because when it rolls out, it is transparent and seamless for us. But, because of that, it costs more, I imagine, than Sisense, or Yellowfin, or Power BI. A lot of those make it sound like they're inexpensive, but when you add in all the hidden costs and all of the overhead, it's probably comparable."
"The price that they offered was around $200 per user license. It was pretty cheap at that time compared to other companies. I think they have revamped their pricing structure since then."
"No matter if you're a developer or an end-user, the licensing cost is around $12 per user per month."
"Oracle products are extremely expensive."
"This was not an expensive product for us, although the price varies depending on conditions for each company."
"The cost of this solution is a little bit high compared with other products like Zoho, so reducing it would make OBIEE more competitive."
"It is reasonable, but it depends on how you're going to use it. There are no costs in addition to the standard licensing fees."
Earn 20 points
Domo is a cloud-based, mobile-first BI platform that helps companies drive more value from their data by helping organizations better integrate, interpret and use data to drive timely decision making and action across the business. The Domo platform enhances existing data warehouse and BI tools and allows users to build custom apps, automate data pipelines, and make data science accessible for anyone through automated insights that can be shared with internal or external stakeholders.
Find more information on The Business Cloud Here.
OBIEE is a multifaceted network of tools that can create a more fluid and better-integrated data flow for your business. This service is actually a platform that is made up of six individual elements, rather than a single tool with multiple features. These services include: presentation catalog, BI presentation service, BI scheduler service, BI server service,administration client, and metadata repository.
The purpose of the OBIEE is to have an entire system for all of your enterprising needs. The various tools within the suite can take your data, organize it, analyze it and then glean the pertinent information from it, sending it on to the relevant parties who can then use it for metrics, pattern analysis, and future projections. The essence of the platform is to integrate your current IT together with their tools in order to give you the overall best return on investment with minimal fiscal obligations.
Domo is ranked 4th in Reporting Tools with 8 reviews while Oracle OBIEE is ranked 3rd in Reporting Tools with 20 reviews. Domo is rated 9.0, while Oracle OBIEE is rated 8.0. The top reviewer of Domo writes "We were able to roll out important KPIs without IT involvement, while eliminating monthly spreadsheet work for senior staff". On the other hand, the top reviewer of Oracle OBIEE writes "Great machine learning capabilities on the cloud with good security mechanisms for larger organizations". Domo is most compared with Tableau, Microsoft BI, Alteryx, Sisense and QlikView, whereas Oracle OBIEE is most compared with Oracle Analytics Cloud, Microsoft BI, Tableau, SAP BusinessObjects Business Intelligence Platform and Qlik Sense. See our Domo vs. Oracle OBIEE report.
We monitor all Reporting Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.