Dundas BI is a business intelligence and data visualization software that includes customizable dashboards, reporting, and visual data analytics. Dundas BI can be integrated into users’ existing business applications and its visualization and reporting tools can be customized to their needs.
N/A
MS SharePoint / SQL
Score 8.0 out of 10
N/A
MS SharePoint / SQL refers to Microsoft Sharepoint, a web-based collaborative platform, being used in tandem with Microsoft SQL Server to provide business intelligence analytics and reporting. They can provide BI content such as data connections, reports, scorecards, dashboards, and more.
For all the scenarios I have so far worked on or I am currently working on, Dundas BI has proved to be more than adequate and apt to handle all of those. It is a very easy-to-use tool with quick shortcuts enabling you to prepare ad-hoc reports or dashboards in a matter of minutes.
A simple and important scenario well suited is that you can configure alerts to notify you when the production server fails. another best feature is the report server is the central component of reporting services. For me something less appropriate is that the admin must ensure optimal performance for farm operations, they recommend that you install SQL Server on a dedicated server that does not run other farm roles and does not host databases for other applications.
Project organization from Development to Production, you get a production and development license but I think the best way to do it is with DEV and Prod project in the Production box. Use the development box for testing updates and really crazy things. With the Dev and Prod projects on the same box, you just publish from Dev to Prod and you are done. Users only have access to the Prod projects so no one can mess up what you are working on.
Security - If you have a hierarchy (subsidiaries, divisions, department, teams) and you want each group to see only their data, then Security hierarchies are for you!
Dependent filters! What's this you ask? Here is an example of how it can be used, in your company you have departments and who works for what department is in your database. You make a dashboard that has a department filter (only show these departments), a managers filter, and employee filter. Not every manager or employee is in multiple departments usually only one. With dependent filters you can say that the manager and employee filter are dependent on what is selected in the departments filter so when you go to filter them they only show the managers or employees that are part of that department, and you can even it do so employees are not only dependent on department but on manager as well. Then it gets even better as it can be done in reverse as well so when you select a manager then go to the department it only shows the departments he works for (there are better situations where this is more useful).
It is scriptable! From calculate columns, null replacements, button actions, load actions, hover over events there a way to do what you want.
They are constantly improving and listens to your suggestions.
Not too many cons for how we use the application. It really is easy and powerful. Very powerful.
Licensing is one thing that could be looked into. It is simple, but a little confusing. For example, if I get a license today, but a new release comes out tomorrow, it seems that the license doesn't work with the new release. Maybe that is by design, but it would be nice to clearly understand.
This was a long-term buy-in from a corporate perspective, to remain in the SharePoint space. Migration is certainly possible, which is good for planning and having options further out. At this point, the only planned migration is to eventually move the architecture up to SharePoint/SQL 2013. At that point, we will be able to leverage some greater efficiencies, some enhanced content design and management features, and some more current social features. It is well worth a full consideration in any shop looking at a new implementation of or migration to SharePoint (although you will probably be considering 2013 versions or beyond in those discussions), but the platform should be a strong competitor to any alternatives. Realizing the capability of a fully-branded and customized website was not part of the original choice for the architecture at Lincoln, but seeing it implemented and functioning now with this capacity far beyond original expectations has certainly cemented plans to continue using it.
We are still in the implementation phase, but so far we are finding it to be easy to use and learn. The eLearning courses that they have made available for free, as well as User Forums and other training videos have made even difficult concepts easier to understand.
SharePoint is very complex. This makes usability somewhat difficult from an IT perspective. An IT generalist will be able to pick it up and run with basic tasks. More customized functions would require significant specialized training and therefore limit what a standard user would be able to achieve. From an end user perspective, it's pretty straightforward to use.
We have bi-weekly calls with our Success Manager, as well as access to support as needed. Any question that I have had, multiple people have been willing and able to jump on a call to talk me through it, or send an email with the solution
It's been fantastic in terms of Premier Support so far. If there is an issue and if you report if the product has an issue, they will act upon it immediately. In some cases, if you design/develop something using the platform, Microsoft appreciates it and... publishes it on their public website. But you have to wait for some time if it is a non-Premier Support issue as you may experience delays.
Per dollar spent, it offers the widest range of features of the tools that we evaluated. It offers lots of options for how to configure your environment, though they are not always intuitive to figure out. Having an ETL layer was a must have for us, as well as the ability to host to secure HIPAA compliance. It is not a replacement for ad hoc reporting, but does a great job of creating parameterized reports and dashboards that look great.
At the time of the two large projects, SharePoint was the enterprise solution so we were required to use that. We have since lobbied the enterprise teams to review and consider Atlassian Confluence and were successful. Confluence is cheaper than Sharepoint which is why we wanted to bring that in. The enterprise has now made Confluence an enterprise solution as an alternative to SharePoint. After using both I think SharePoint has many more add-ins than Confluence. It has much more customization ability than Confluence. SharePoint is not good for mobile readiness. Confluence is so there is a difference that might lead you to Confluence over SharePoint. I would also say that SharePoint is very document-centric and that Confluence has better KM than SharePoint does. even with the use of SQL Server. We were told that we could not use Google Drive even though it had features we liked.
I've installed SharePoint in many different industries and each industry has seen greater collaboration among their teams both locally and nationally. The ability to collaborate more efficiently has reduced the need to have employees centrally located.
Companies which have used SharePoint in a end user training portal have had great ROI, since they can create the content once and share with all their users who subscribe to their training service. The web content management aspect of SharePoint is a very helpful feature.
