Home » sharepoint » Comments on Implementing SharePoint for Enterprise Business Analytics

Comments on Implementing SharePoint for Enterprise Business Analytics

In its most recent quarterly earnings report, for Q2 2014, Microsoft® reported a 25% year over year increase in sales of SQL Server. I take this jump in sales as an indicator of the substantial interest enterprise business, and comparably sized organizations in the public and not-for-profit sectors have in gathering highly useful Business Intelligence (BI) from their data.

SharePoint 2013 includes a lot of features these organizations can implement to successfully attain their BI objectives. In a video tutorial series titled SharePoint 2013: Business Intelligence, Jason Himmelstein, a SharePoint MVP, ITPro Solution Architect, and an author of “Developing Business Intelligence Apps for SharePoint” (published by O’Reilly), presents a number of them. This video tutorial set is suitable for an audience of SharePoint Administrators, developers, designers and architects.

SharePoint Partners in the business of delivering custom BI solutions for their clients can also provide them with this video training set. The industry best practices demonstrated in the set are highly reliable, proven techniques likely to support any successful implementation of a custom BI solution for a specific community of SharePoint users. A decision to provide customers with this training set, in lieu of producing custom video tutorials for the same purpose, obviously save time, expense, while keeping down customer costs for acquiring the custom BI solution. So I think it makes sense to at least think about our set before embarking on a custom production of the same techniques, features and methods.

In any case, SharePoint stakeholders benefit from a tutorial set like ours. Industry best practices are dependable and widely used, so identifying professional services firms capable of implementing any of them is an easier task. It’s important to note the comparatively miniscule amount of actual coding included in this set as another reason to consider it. Using workflows to achieve the same of objectives otherwise restricted to hard coded systems almost always ends up in cost savings for the organization opting to proceed in this manner. Of even more importance, the task of managing, or remediating workflows is much easier than is the case for a hard coded solution, especially one written by a developer who may have neglected documenting some important features, and is otherwise immersed in another project with no time to spare.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved