SharePoint Reviews

It's used as the intranet portal. It is used to inform the users about upcoming activities in the company.

To share information and latest news. We can monitor when the content is being updated, and we can see who the person is.

The list library. And also the document libraries. And also other apps like survey which is heavily used in the company.

• Advise users to update the content.
• Maybe allowing users to change their background and text by themselves.

• Company intranet and extranet.
• Enabling the employee workforce to be more efficient in their day-to-day work they need to deliver for the organisation.

• Document management and sharing with user-controlled security
• Ability to use lists, document management, and workflow to manage the hand-off of work efforts internal to the organisation.

• Document libraries (tagging and search)
• Lists
• Workflow (added)
• Security
• Alerts
• Publishing features and co-authoring.

It is functionalities that improve the efficiency of the employee workforce.

• Better collaboration, and team sites (social flavour) mobile enabled

• More and improved integration capabilities into the eco-system of solutions available.

I have been using SharePoint for over twelve years. 

It's a big solution comprising many services similar to an active directory installation with connections to Skype, Exchange services, metadata services and stuff like that, it can do basically everything you need in order to deliver something like a Twitter website or similar solutions. So I do not think that anything rivals SharePoint on the market. Maybe if a lot of effort is placed upon some WebLogic solutions, this may happen. But, this would need a lot of customizing.

So if you want to have something like a business, or if you want to have something like a product catalog and you are selling something like Amazon, you want to uniquely identify your product like Amazon does it with its ASIM numbers and these to be identified with a name. So the service identifying these unique ASIM in numbers with their names which might be localized in English, German, Dutch or other languages. These are being identified by a managed Metadata service. Amazon does something very similar to Metadata and SharePoint. So, that's the basic technology everyone needs for this web service experience and order to identify the same object with different names.

The metadata services, the WCF service integration and the Voxel feature are three most valuable elements of this solution. The Voxel feature, for obvious reasons, because you want to implement business processes and you do not want them to stop if the machine stops so they have to be automatically started. This is What the Voxel feature in SharePoint does. The managed Metadata allows you to define your own notions or terms denoting notions within your companies. And I if I want to disarm them, or disarm power supplies of different types, I need something to denote the names pointing to entities, any program can identify.

Perceptively it does what people used to do with the pens and pencils, on paper. For Millennials, by taking a note of what to do on the paper or stone or whatever they have been using and let anyone else read it and execute with it. So what any back flow or business process you have did legal one for King Nebuchadnezzar 2,700 years ago or for any business where you are taking a phone call, we two are doing right now and writing down something or I have to remind myself to do whatever and sent that over to pop and be while having receipts from department A and have to digitally sign it and send out the paper. It streamlines everything for us.

All of this business processes, people have been performing solely within their minds. Maybe automatized with the structural feature, but it depends on all the metadata that has been stored within the managed metadata, service, user profile data or whatever. So you can not just say, "Oh, I want to send a car" to whom do you want to send it to. Which car do you want to send? So, all of these parameters have to be stored somewhere else. This is what drives the business process and SharePoint solution allowing you to automatize them.

I would be liking to see the talk features included in SharePoint because Microsoft effectively discontinued this talk and put something like logic apps but only for Azure, and most German companies do not like Windows Azure because they do not want to put that data into a cloud where everyone can see it. So, there's a lot of distrust with Azure environments and you need something to have on premises as a similar solution. And this talk is something like a big playing ground. For instance, if you want to play monopoly and anyone wants to move the pieces but moving the pieces on street A to street B means you are changing your business process from, I have been starting tax declaration, to I've been finding it but not yet sending it out. So, if you wanted to have something like a business process be denoted as a board game, which is what Monopoly did in 1945, effectively.

It is very stable if you know what you are doing and make some precautions. Microsoft lists these precautions, but these precautions are not automatized. It would be nice to have precautions such as: disk size, backup checks, or whatever automized that can be integrated with the SCCM team foundations server.

Well, that's one of the strengths because it not just using soap web services where it sends some XML file to different machines, but it's using WCF, which is a version of a web service, web services being used if you have a different machine where you want to call a function. The type of machines we are using now are invented by Alan Turing, a guy from the hacking Enigma code and Robert Dennard, who invented RAM. These types of machines do not allow you to, all functions on the remote machine. If you want to do that, you have to send a hint which is what web services does.

I have been using the commercial technical support and they're always professional. It's not cheap, but they are always professional. So if there's problems to be solved, Microsoft tops off as excellent.

The initial setup was very complex. We had to keep in mind all of the backup solutions. It is kind of like remodeling a kitchen. You must think of all of the parts, the architecture, the electricity, the air flow, etc.

I think that SharePoint is the best on the market in terms of stability, quality and capability. I also suggest that if a company has chosen SharePoint, the company must have at least a two day training prior to implementation.

The cost is expensive, but worthwhile.

It's good but we are not using a lot of load in the system.

It's the look and feel and maybe the integration with the Office platform.

Basically, it's just for internet and communication. It's not a busy implementation.

We need the storage of the files, the documents right now are in the database. Maybe SharePoint has to improve the capability to store the information in file systems. In theory right now, it could do that. But, I understand that some functions are lost when you store the information in a file system, so maybe that's a way SharePoint can improve.

It is very stable. But, I think it depends on the infrastructure. 

It's scalable because you can add more and more SharePoint's installations and maybe you can divide the content and everything, so it's scalable.

We have not yet had a need to contact tech support.

We use it for collaboration and document management in the process of developing proposal responses.

SharePoint has made it easier to collaborate across the company during the process of developing proposals.

• The collaboration is incredibly helpful. 
• The ability to have version control and co-editing is vital to our workflows.

SharePoint sometimes cannot handle the amount of co-editing that we do. Of course, this could be the user, not the tool.

Enterprise collaboration.

• Helps with document collaboration and workflow.

• Provides us with a records center.

• Records center

• Shared calendar.
  

• Ease of use.

• Improvement on the user interface (UI).

Collaboration and document sharing are the primary reasons for using SharePoint. We have used the product in many government agencies for documents management, workflow, enterprise search, departmental solutions, Intranet, etc.

SharePoint is a big product with many features including customization flexibilities. We have deployed it in many government agencies which were in much need of process and automation improvements.

The product makes it easy to manage lists, forms, searching, and security. One of the most valuable features is its integration with Active Directory.

• Processing data from multiple site collections is not easy as they reside in different databases. 
• The management of the product/back-end is complex.

We have purchased add-ons to handle multiple site collections, form creation, and design. 

My primary use case is largely content management. The product is good.

• Information is much more readily available. 
• There is more functionality available.
• It allows for simultaneous users to be on it.

A combination of:

• Auditing
• Logging
• Collaboration.

It has been very useful and easy to use.

It should have more user-friendly customization, as it still requires developers to get engaged and build sites.

I would like it to be more compliant with global regulations. There are certain features which could be included that currently are not there, such as compliance and record management capabilities.

It is very stability. I don't foresee any issues.

I have not faced scalability issues.

I would rate Microsoft technical support as a six out of 10. They are just okay.

Previously, we were using file share. We switched because SharePoint made things easier with the increased functionality for building the portals, microsites, and total integration with Microsoft categories.

The initial setup was fairly complex, but that may just be our environment. A fair amount of design and consolidation needed to go into it.

With this product, have a decent skill set in-house. 

Most important criteria when selecting a vendor: support.

Compared to other products, SharePoint is not only a content manager, but a wider product, like enterprise content management. You can use multiple components in SharePoint. Moreover, SharePoint is already moving to cloud, if you are using SharePoint online, which is cloud-based technology, it is more accessible. 

• Data classification
• Search

These two elements are cheap.

We would like more security features, like automating. 

There are some limitations on storage. 

The product and technical support teams are really good.

The initial setup is straightforward.

The replacement costs for it are cheaper if you use only SharePoint.

The use case is based on internal processes. We want a central place for storing data, documents, and user processes, to automate processes.

In this case, it's a financial program. All customers starting our financial program are automatically created on SharePoint. From there, all the documents that are related to each customer will be stored on SharePoint, and we then use it as a kind of a black box. You put everything in, you do not know where it is. Then we have other applications around it that give you information that you need. Or you can save it and, based on customer information or the kind of document, it knows where to store it on SharePoint.

It manages processes. I personally think a very strong point is that we use it in combination with OneDrive. Now that we have been handed the GDPR law enforcement, in combination with OneDrive, we can synchronize documents or part of a customer's information to a laptop. If they make changes it will automatically be synchronized back. In the case of a lost or defective device, you always have the information. I think this is a very strong point.

It's stable. It's very widely used by companies. Also, the knowledge of the product has improved over the years, and by other companies that support it or are Microsoft SharePoint partners. So if there are problems, there's always a user or company that knows the information or can help you; even with very uncommon problems.

Another strong feature is the search engine. It can search all documents. It can find everything.

We also have our own developers. What we want with SharePoint, we can program it and create many reports, every kind of information needed. Developers can easily create an application for it and display this information.

We are mainly using third-party tools for it, at the moment, for automating processes. In the new version, for 2019, I know that some of the processes are finally in SharePoint. They are a now using third-party tools for it.

Also, the integration with Outlook could be improved.

It's fairly easy to scale. You can just add front-ends to it. Just a little installation and it's done. It's very easy to expand.

Technical support is very good.

The switch was handed to our default supplier of software, in this case, Microsoft. The whole platform we used was based on Microsoft.

It's not a vendor we select, we select a product. After that, we look at the vendor. If the product looks good, promising, and it looks stable - and of course we test it before we go any further with it - then we look at the vendor, especially the support. Then we find other cases, where they have implemented a similar product or feature and ask for their feedback.

A partner initially installed it. That was the start of our use of SharePoint. I believe there was a lack of information or a lack of knowledge on the part of the external party that initiated this project. As our internal IT department has improved, the setup of SharePoint - we migrated to a new version - has improved.

My advice would depend on the use case. SharePoint, for us, is the most suitable because we use mainly Microsoft products. So for us, it's the way to go because the integration is solid. If colleagues have other products, it depends on what they're asking. Look at the best option. It's not that I'm saying, "You have to use this product because it's the greatest." Consider what you need, what you want.

It's very stable. I don't call it a document management system, I call it a multifunctional document system. You can do a lot of things with it. It's just incredible how much. I really like that we have been able to automate a few steps that people had to do. Also, this process was only possible with SharePoint, because of the integration of other Office products. We're using the basic Microsoft suite and integration was a very big part of it.