What is our primary use case?
We primarily use the solution for our data visualization, our different types of data. It is linked to our normal data visualization. It's not usually related to the medical side of the business. However, it is related to the revenue, and financial accounting, and submission on the RCM side.
What is most valuable?
If I compare Tableau with Power BI, I prefer Tableau. It's easier to use.
The solution has very good drag-and-drop functionality and the screens are easy to navigate. You can easily create measures and dimensions. It has a user-friendly layout that makes task completion simple. In comparison, in Power BI, all of these actions are quite cumbersome.
It is quite similar to Excel. If a person has good Excel knowledge, it will be quite intuitive to learn.
Tableau is the whole package.
The solution allows you to write in SQL and Python. We don't need to write the Python code and we don't need to write the SQL script. However, it is an option that's on the table.
The solution is very stable.
You can scale the solution well.
It's very easy to set everything up.
What needs improvement?
There is another ETL tool for Tableau that is new. It takes time to reach some level of experience. IN Power BI, they have Power Query. I find it easier to convert the information in Power Query with a single shortcut key. That's not an option in Tableau.
You have to prepare your data. It will take a lot of time to clean the data.
There's no mature ETL tool in Tableau, which is quite a negative for them. They need to offer some built-in ETL tool that has a nice and easy drag-and-drop functionality.
There needs to be a bit more integration capability.
For how long have I used the solution?
I've used the solution for about six months to one year. It wasn't very long. I used it at my previous organization. We're also using it at my current company. At this organization, we've only had it for about three or so months. It's quite new here.
What do I think about the stability of the solution?
The solution is extremely stable. It's much more stable than, for example, Power BI. There are no bugs or glitches. It doesn't crash or freeze. It's very reliable. The performance is great. We've never faced any stability issues while using the product.
What do I think about the scalability of the solution?
I'm not sure how many users we actually have within the company.
Tableau is one package and there isn't too much complexity. The main pieces are Tableau itself, Prep Builder and Tableau Server, and Tableau Mobile. Sorry, Tableau Online. These four are the most basic software pieces of Tableau.
Whenever you purchase Tableau, you will pay a bit more and more. You will have access to the four main software products. After this, there is no need to purchase something extra. Therefore, in Tableau, there is no scalability issue. In comparison, if you will to Microsoft, there is a lot of products - such as Power BI. There is Power Automate RPA and Power Apps and MicroPower Apps also. You will need to call to Microsoft and they will integrate this Power App with your account. It takes time. With Tableau, there isn't an issue like that.
How are customer service and technical support?
We haven't had any sort of technical issues. They did assist us a bit at the outset. and they were very good. They are always online and easily approachable. We're quite satisfied with their level of service.
Which solution did I use previously and why did I switch?
How was the initial setup?
The initial setup was very simple. It's not a complex process.
They have an excellent team here over at Tableau. They assisted us.
The setup wasn't too difficult due to the fact that our system is not very complex. We work with rather simple data, which helped save us from suffering through many complexities.
Maintenance is required at our database level. Our database is smart and lean, and therefore it's pretty straightforward. However long it takes for maintenance tasks is based on the level of data and on the heaviness. We basically do a sort of troubleshooting and some fine-tuning at the database level.
At the time of making visualization, we have to do some research to load everything properly on Tableau and have a refresh rate we can maintain. There should not be too much of a refresh rate every time.
What about the implementation team?
We had Tableau's technical team help us here and there. They were great and we were satisfied with their help.
What's my experience with pricing, setup cost, and licensing?
The pricing is $70 per month. You have to pay about $800 or something in that ballpark annually for one license.
What other advice do I have?
We are a customer and an end-user.
We are currently using the latest version of the solution.
I would recommend the solution. If a company really wants to go for some easy solutions, and something that is robust and dynamic this is a great option. Microsoft's Power BI also has its advantages and could be a good option as well, depending on what a company needs. If Mircosoft offered a bit more, we might even consider switching over. However, for us, Tableau is the better option.
I'm using Microsoft Power BI also. Therefore, personally, I see the importance of the ETL tool. Microsoft is also adding many items rapidly - with new features two or three times a month. Tableau isn't making such advances regularly.
Many people are considering shifting from Tableau to Microsoft very seriously. Therefore, Tableau needs to begin to compete. They need to offer more integrations and invest in a robust and easy ETL solution. It would really assist in cleaning the data.
If a company wants to onboard Tableau, they need to have some sort of ETL tool on the side as well. If they don't, and they don't have SQL or Python, I'd actually direct them to Power BI - simply to get that ETL capability. However, if the data is ready, and no ETL is required, Tableau is an excellent solution. If you just need to visualize the data, Tableau is the best.
Overall, due to the lack of ETL, and the inability to effectively clean the data, I would rate the solution at a six out of ten.
Which deployment model are you using for this solution?
Which version of this solution are you currently using?