Cooperlink CONNECT enables a real time two ways integration between Asite and Microsoft SharePoint.

In other words, when there is a new version of a project document (plan, model, product datasheet, report…) in SharePoint satisfying some criteria, it is pushed automatically into Asite or vice-versa. From a user perspective, it means you always access the latest version with no need to connect to the other system.  

Why does that matter?  

• Forget the upload & downloads: These manual operations are replaced by an automated process.
• Directly find the latest version. As an Asite or SharePoint user, you are sure to find and use the version that matters. Avoid the risk of working based on an outdated version and stop losing time validating which version is the good one across different systems.
• IT systems should not be islands: SharePoint and Asite meet overlapping businessneeds. SharePoint is primarily designed for internal collaboration purposes where Asite allows to collaborate with your external partners on a construction project. Data is not only for internal purpose or external. Having related systems that don’t work well together and not correctly updated will lead to errors and frustration for the users.
• Enforce your Data security & Governance standards: Having the data stored in one central place is the way to meet Security compliance and protect your organization against data lost (https://www.cooperlink.io/challenges/secure-centralize-and-own-your-data-prevent-losses-and-claims).
• Impress your customer: Is your customer willing to always have the data of the project in their SharePoint environment? No problem. You can answer ‘yes’ and activate the link within days.  

Why Cooperlink as link between Asite and Microsoft SharePoint?

Integration between commercial platforms can also be done via custom developments. So why using Cooperlink ?  

The challenges with custom development are the complexity and the maintenance. Let me explain :

• Integration works are complex. Manipulate data across systems can be tricky (eg how do you detect that a file has been moved or renamed) and connecting to different systems means learning new API's.
• API of commercial products tend to change quite often.
• Monitoring needed

‍

Therefore,we offer another way:  

• We take care of the initial implementation and later upgrades whenever a new version of the APIs is released.
• We take care of the monitoring. If a file has not been correctly synchronized, we will manage and solve the incident.
• Costs are predictive.

In short, all-in and available within days instead of months.