We mainly work as visualization experts for an organization. We know how Dundas BI works, what are its capabilities, and how to deploy the reports for multiple users by using the layering structures, etc. It is basically purchased by the clients, and we end up working as the developer for Dundas BI.
I have been working with reporting groups. For one of our clients, we had a requirement where we had to create reports, and Dundas BI was the tool that they were using at that particular time. It was back in 2016 when I worked for around 18 months on Dundas BI. The client had already upgraded to Dundas BI at that time, and they were using it as a solution for an end client in the Oil and Gas domain. We ended up creating more than 500 different dashboards for them by using Dundas BI. I was working with a team of three or four developers who got onboarded to Dundas BI.
Six months ago, I again worked for the same client, but it was a different end client of theirs. The end client's domain again was Oil and Gas. We ended up using a lot of features in Dundas BI. They were connecting to multiple data sources in Dundas BI, and they had a semantic layer in between to allow them to connect to the database. They also had a KPI system. They were connecting to more than 40 different sources while creating cubes in Dundas.
It was on-premises. It was not on the public cloud because there were data security concerns for them. They had multiple licenses, and it was a pretty big implementation for them.