Now the power of SharePoint: Where SharePoint is often used and what makes the end user so happy with SharePoint. The management of who has what rights to what is imposed from an Enterprise level.The location of the document and the values of the (other) metadata is recorded at enterprise level and is therefore available to everyone within the enterprise clear and unambiguous.The properties / meta-data of a document / file are determined by the demands on enterprise level.
![use ecm tools use ecm tools](https://cumminsdieselmotor.com/wp-content/uploads/Cummins_Isx_Ecm_Ecu_Cpl_2733_Diesel_Engine_Computer_Module_Egr_Part_3684275_06_vda.jpg)
The roles and groups that the solutions are used at an enterprise level and are clearly managed at that level.Documents rights are managed centrally and can be easily shown / reviewed.Some examples of requirements for an ECM solution: Supporting the Enterprise by managing unstructured information which is important to the enterprise and ensuring that the requirements and wishes of the Enterprise around this information are being safeguarded and secure. The goal of ECM: After a long road of many different opinions and views it has become gradually clear what ECM solutions are: Leaving you a mess to clean up later.īut as SharePoint can separate content from data, it is good to make an ECM solution? To answer this I’ll leave the technique behind and focus on the purpose of an Enterprise solution and the power of SharePoint. When someone introduces SharePoint within a company often their ECM knowledge is limited to none and so they will not turn on this feature. Strangely, the fact still remains that it is not the default. Microsoft is of course not so stupid, despite heavy pressure from the MS SQL team it is possible to use a FileShare as a standard feature in document storage and SP2010 now works well and quickly with this feature. So storing Documents in RDBMS BLOBs is an easy technical No-No.
![use ecm tools use ecm tools](https://www.opentext.com/file_source/OpenText/en_US/JPG/opentext-salesforce.jpg)
One or two BLOBs within the whole database are no problem, but within an Enterprise it is never small and will always be relative large amount of BLOBs/documents. The base concept of a relational database is focused on structuring similar information pieces. After a while the database will shut down (performance wise). That is the tricky one! In the end only the use of simple and clear examples works best.įor people who know something of the technique behind SharePoint I probably don’t have to explain what the challenges are when you use too many BLOBs in a relational database. The only problem is convincing the decision makers. The longer I’m in this business the simpler I find the answer.
![use ecm tools use ecm tools](https://www.infotivity.com/ecm-requirements.png)
![use ecm tools use ecm tools](https://www.u-obd.com/wp-content/uploads/2019/09/08G5151-Car-ECU-Commonly-used-ECM-driver-chips.jpg)
Why an ECM tool when I can create a link in Oracle to a document?.Why an ECM tool when I can store documents also in SAP?.In the 25 years that I’m involved with IT and more specific Enterprise Content Management these are the questions that are most difficult to answer and the discussions are typically long: So: What is SharePoint 2010 and what is it not? Sure SharePoint 2010 has its records center and sure you can build/develop a good Enterprise Content Management solution, but is that what you want? Or should we not forget the phrase, “Stick to what you’re good at”, when it comes to IT and flexible tools like SharePoint.