Overview

RDrive DataBridge provides a way to connect RDrive with other platforms used across your projects and organisation.

Rather than manually transferring information or documents between systems, DataBridge can be configured to transfer agreed information from RDrive to an external platform when specific events take place.

For example, a completed Form in RDrive could automatically be transferred to your document management platform when it reaches an agreed status.

DataBridge sits behind the integration and is configured and managed by the RDrive team. You do not need access to DataBridge or need to configure the technical connection yourself.

How Does RDrive DataBridge Work?

The exact workflow depends on the platform being integrated and your requirements.

A typical integration follows this process:

Activity takes place in RDrive
A Form or Process is created, updated or reaches an agreed status.

↓

The agreed integration trigger is reached
For example, a Form reaches Closed or Approved.

↓

RDrive DataBridge processes the information
The relevant document, data and configured mappings are prepared for the external platform.

↓

Information is transferred to the connected platform
The document and associated information are transferred according to the agreed integration configuration.

This allows integrations to be tailored around your existing project processes rather than requiring every customer to follow the same workflow.

What Can Be Integrated?

The information available for integration depends on the connected platform and the agreed workflow.

An integration may include:

• RDrive Forms and Processes
• Generated Form documents
• Form statuses
• Document titles and references
• Status dates
• Revision information
• Form field information
• Project information
• Other metadata required by the connected platform

Not every integration will use all of these.

As part of the setup process, the RDrive team will work with you to determine the information required for your integration.

Integration Triggers

DataBridge can use events within RDrive to determine when information should be transferred.

For example, you may want a document to be transferred only when a Form reaches a particular status.

A typical requirement might be:

When a Fire Stopping Inspection reaches Closed in RDrive, transfer the generated document to the agreed location within the connected document management platform.

Different Forms and Processes can have different integration requirements depending on the connected platform and your project workflow.

Mapping Your Information

RDrive and the platform you are connecting to may use different terminology, statuses and metadata.

As part of the integration setup, we will therefore agree how information in RDrive should correspond with information in the connected platform.

For example:

The exact mappings available will depend on the platform being integrated.

The RDrive team will configure these mappings for you. You do not need to configure DataBridge yourself.

Setting Up an Integration

Although the exact requirements differ between platforms, there are typically three stages to setting up an integration.

1. Access

RDrive will confirm what access is required to establish the connection with your chosen platform.

This may involve creating a dedicated integration account, providing access to a project or workspace, or completing another platform-specific authorisation process.

The relevant integration guide will explain exactly what is required.

2. Synchronisation Requirements

We will work with you to understand what should be transferred and when.

This normally includes identifying:

• The RDrive Project
• The RDrive Form / Process
• The event or status that should trigger the transfer
• The destination platform
• The destination project, workspace or location

3. Mapping Requirements

We will then establish how the information from RDrive should be represented in the connected platform.

Depending on the integration, this may include statuses, document types, titles, references, revisions and other metadata.

Once these requirements have been agreed, the RDrive team can configure and test the integration.

Available Integrations

DataBridge integrations are configured according to the requirements of each supported platform.

Asite

RDrive can integrate with Asite to transfer agreed RDrive Forms and associated information into your Asite environment.

The setup includes establishing access to Asite, agreeing which RDrive Forms and statuses should trigger a transfer, identifying the required Asite destination and defining the required document and metadata mappings.

Read next: Setting Up an Asite Integration with RDriv

Aconex

RDrive DataBridge supports integration with Aconex. The integration can be configured according to the required RDrive processes, mappings and destination requirements.

Read next: Please contact your RDrive representative 

Microsoft SharePoint

RDrive DataBridge supports integration with SharePoint, providing a way to transfer agreed RDrive information and files into the required SharePoint environment.

Read next: Please contact your RDrive representative

AutoDesk

RDrive DataBridge supports integration with AutoDesk providing a way to transfer agreed RDrive information and files into the required SharePoint environment.

Read next: Please contact your RDrive representative

Looking for another integration?

If the platform you would like to connect to RDrive is not listed above, please contact your RDrive representative to discuss your requirements and available integration options.

What RDrive Will Manage

Once the requirements have been agreed, the RDrive team will manage the technical DataBridge configuration.

Depending on the integration, this can include:

• Configuring the connection to the external platform
• Configuring the relevant RDrive Forms and Processes
• Configuring integration triggers
• Creating the required data mappings
• Mapping RDrive values to corresponding platform values
• Configuring document and metadata requirements
• Testing the integration
• Validating that information has been transferred successfully

Customers do not require access to RDrive DataBridge.

Testing Your Integration

Before an integration is put into normal use, it should be tested using an agreed example.

The RDrive team will work with you to:

1. Create or identify an appropriate test record in RDrive.
2. Move the record through the required workflow.
3. Confirm that the configured integration trigger has been reached.
4. Confirm that the information has been transferred.
5. Check the resulting document and metadata within the connected platform.
6. Confirm that the result matches the agreed mapping requirements.

Any required configuration changes can then be made before the integration is used as part of your normal project workflow.

Making Changes to an Existing Integration

Your integration requirements may change over time.

For example, you may need to:

• Add another RDrive Form or Process
• Change the status that triggers a transfer
• Add or change a destination
• Update a status mapping
• Change document metadata requirements
• Add another project

Please contact your RDrive representative before making changes that may affect an existing integration.

We can review the requirement and confirm whether the DataBridge configuration needs to be updated.

FAQs & Troubleshooting

Q: Do I need access to RDrive DataBridge? 
A: No. DataBridge is configured and managed by the RDrive team. 

Q: Do I need to configure the integration myself? 
A: No. We will work with you to gather the required access, synchronisation and mapping information and configure the integration on your behalf. 

Q: Can I choose when information is transferred? 
A: Where supported by the integration, yes. For example, a particular RDrive Form status can be used to determine when a document should be transferred. 

Q: Can different Forms have different integration requirements? 
A: Yes. Different Forms or Processes can be configured according to the agreed integration requirements. 

Q: Can RDrive and the connected platform use different statuses? 
A: Yes. Where supported, mappings can be configured between RDrive values and the corresponding values required by the connected platform. 

Q: Can we change the integration later? 
A: Yes. Contact your RDrive representative if you need to change an existing integration. We will review the requirement and update the configuration where appropriate.

Q: What happens if information is not transferred? 
A: Contact RDrive Support with details of the affected RDrive record, including the Project, Form / Process and expected transfer. The RDrive team can investigate the integration and determine where the transfer has stopped.