Why Use SharePoint in a Corporate Environment
Updated April 25, 2015

Why Use SharePoint in a Corporate Environment

Qamar Zaman | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Software Version

2007, 2010, 2013 and SharePoint Oline

Modules Used

  • Publishing, Collaboration, Document Management, Workflow, InfoPath, etc.

Overall Satisfaction with MS SharePoint

In my current role, I have incorporated SharePoint in a variety of ways and perhaps that's its greatest attraction and benefit. SharePoint is an enterprise product and we needed to have a number of business use cases to justify its costs. For us the cost of the platform, licensing, resilience, DR, support etc. all need to be considered before it became the platform of choice. Luckily for most organisation, although not the case for my current company due to sensitive data, cloud hosting including Microsoft's Online offering do away with the initial steep curve to embed it in.
Even given the initial capital outlay, it is a far more cost-effective option if you consider a plethora of alternatives that need to be procured to provide the same set of functionality. In our case we have used it for;

  1. The intranet

  2. Customer Portals for our partners. that incorporate surfacing data from our other enterprise systems; Oracle, SAP, IBM, Maximo etc.

  3. Health and Safety System.

  4. A number of document management sites for various departments, migrating from other expensive products.

  5. Collaboration to increase security and reduce load on Outlook (constant attachments etc.).

  6. There are a number of other projects that we're considering that will go on SharePoint.
It's integration with Outlook, Lync, SCCM, SQL Reporting, Office Web Apps (OWA), Microsoft Dynamics is the next set of challenges that will eliminate the need for a number of scattered systems and bring a coherent search experience.

  • The intranet - SharePoint has a mature publishing framework with workflows, content approval, versioning, multi-lingual site and so on.
  • Collaboration and Social Features that include complex workflows for documents, multi-user updates, rich metadata association, and much more
  • Surfacing line of business data (Business Connectivity Services) and providing ability for rich Dashboards and KPI with integration for Excel graphs (Excel services) and SSRS and a host of other features that provide powerful analysis and reporting capabilities.
  • Lists of various types with configurable columns, alerting, and email integration rich taxonomy, secure access - all without writing a single lin eof code.
  • Ability to search not only data held within SharePoint, but also on disk shares, outlook and other systems (eDiscovery).
  • SharePoint has seen improvements in workflow, but I feel the process for end user can be further simplified.
  • I'd like to see LightSwitch somehow integrated to provide building relational applications (similar to force.com in some ways).
  • The Client-side Object Model needs to be further developed.
  • It has allowed us to put a number of applications on SharePoint that we had no other place to put them - other than to procure dedicated solutions.
SharePoint is extremely well suited to Intranet, Document Management and a host of 'tracking' type applications.
It is not well suited to put relational application on it, although there is some limited relational support.

Using MS SharePoint

For me it is the most cost effective solution to a number of separate products which would otherwise require not only the procurement of a number of individual products, but also;

  • Separate agreements

  • Separate infrastructures

  • separate Support

  • Separate Logons potentially

  • Incoherent search across all systems, if one was available

  • Separate renewal, upgrade, patching etc.

MS SharePoint Implementation