Synchronize Assets between Eptura and Tandem
After assets are onboarded from Tandem to Eptura, we can synchronize asset data changes bi-directionally between Eptura and Tandem. Asset data can be synchronized by floor or by building. Currently, synchronization is manually initiated from the Tandem configuration screen.
Update Asset Details in Eptura
After onboarding, updates to the following Eptura Asset fields can be synced back to Autodesk Tandem.
asset id, asset description, manufacturer, model, status, location
Update Asset Details in Tandem
After onboarding, updates to the following Autodesk Tandem fields can be synced back to Eptura Asset.
Eptura manufacturer, Eptura Model
Sync Assets
After onboarding, the Sync Building button and Sync Floor icon will be enabled in the Autodesk Tandem configuration page:
Use Sync Building to sync all floors of a building. Use Sync Floor to sync an individual floor of a building.
If there are data conflicts, due to changes being made in both Eptura Asset and Autodesk Tandem; e.g. Manufacturer was updated in both places, the changes made to Eptura Asset will persist.
Known Limitations
Autodesk Tandem includes a concept of Element and Type Properties.
From the Autodesk Knowledge Center:
Each element of the model is an instance of a family type. Element parameters apply to all elements that belong to a particular family type, but the values of these parameters could be unique for each instance of the element. An example would be a serial number or installation date.
For example, your BIM model may contain a number of pumps. There may be many different types of pumps of various manufacturers and models. A pump of a particular manufacturer (Bell & Gosset) and model (4GC) belong to single family type. Manufacturer and model are type properties and are the same for all instances of the element in the model. A pump may also have other properties like id, name, and serial number. These are element properties and can vary for each instance of the element in the model.
When updating type properties like manufacturer and model in Autodesk Tandem, they will be updated for all instances of the element in the model. This data can then be synced to Eptura Asset.
When updating type properties like manufacturer and model in Eptura Asset, they will be updated for a single instance of the asset. When this data is synced to Autodesk Tandem, it will result in updating the manufacturer and model for all instances of the type.
Users should be aware of this behavior when updating manufacturer and model. Eptura is currently working with Autodesk on a solution to better address this in the future.
Eptura to Autodesk Tandem Data Mapping
This section contains information about the data mapping between Eptura and Autodesk Tandem, as well as what behavior to expect when onboarding and syncing data.
If you want a better table layout, then we recommend you click the left-menu toggle to turn off the menu and then the table displays wider.
|
Eptura Asset Field Name / Description |
Unique |
Required |
Tandem Field Name / Description |
Onboard |
Sync |
|---|---|---|---|---|---|
|
tenantId Foreign key to Tenant |
✓ |
✓ |
Tenant Id is generated during onboarding. e.g. 3fa85f64-5717-4562-b3fc-2c963f66afa6 |
Onboard to Eptura |
|
|
id Primary key to Asset |
✓ |
✓ |
Eptura Asset Id Asset Id is generated during onboarding. e.g. b0d68775-ebea-4c67-8aa8-3d1a7c3e7387 |
Onboard to Eptura Onboard to Tandem |
|
|
parentAssetType or category Parent Asset Type Name |
✓ |
Eptura Parent Asset Class Description Derived from the Tandem classification e.g. Mechanical |
Onboard to Eptura |
||
|
assetType or subCategory Asset Type Name |
✓ |
Eptura Asset Class Description Derived from the Tandem classification e.g. Air Handling Unit |
Onboard to Eptura |
||
|
group Group Name |
All assets are onboarded with the default group: Tandem Operations |
Onboard to Eptura |
|||
|
assetIdentifier or assetId Asset Code |
✓ |
✓ |
Eptura Asset Code Asset Identifier is calculated during onboarding. e.g. LTU-RF-ME-AHU-0001 |
Onboard to Eptura Onboard to Tandem |
Sync to Tandem |
|
name or description Asset Name |
✓ |
✓ |
Eptura Asset Name Asset Name is calculated during onboarding. e.g. Air Handling Unit LTU-RF-ME-AHU-0001
|
Onboard to Eptura Onboard to Tandem |
Sync to Tandem |
|
manufacturer Foreign key to Manufacturer Name |
Eptura Manufacturer Manufacturer is created by Back sync service (if it doesn't exist) during onboarding. |
Onboard to Eptura
|
Sync to Eptura Sync to Tandem |
||
|
model Foreign key to Model |
Eptura Model No Model is created by Back sync service (if it doesn’t exist) during onboarding. |
Onboard to Eptura |
Sync to Eptura Sync to Tandem
|
||
|
status Status Name |
✓ |
Eptura Status Assets are onboarded with a default status: ACTIVE |
Onboard to Tandem |
Sync to Tandem |
|
|
siteId Foreign key to Site |
Site Id is looked up in the Location service during onboarding. | Onboard to Eptura | |||
|
locationId Foreign key to Location |
Eptura Location Location Id is looked up in the Location service during onboarding. Tandem location is calculated after onboarding: Site Name | Building Name | Floor Name | Space Name |
Onboard to Eptura Onboard to Tandem |
Sync to Tandem |
||
|
integrationAssetId Asset Integration Id (Tandem Element Id) |
✓ |
Asset identifier in Tandem e.g. AAAAACDlEY_-C0j9gKJ98yROarkAIFWD |
Onboard to Eptura |
||
|
integrationGroupId Asset Integration Group Id (Tandem Facility Id, Tandem Model Id) |
✓ |
Asset Facility and Model Identifiers in Tandem e.g. urn:adsk.dtt:knSiBIexTACwnRyQHFaZJA;urn:adsk.dtm:Q80B32BqSFKqdv6Z49-78g |
Onboard to Eptura |
||
|
integrationType Asset Integration Type |
✓ |
Assets are onboarded with a default Integration Type of tandem. |
Onboard to Eptura |
||
| Deep link to Eptura Asset Detail |
Eptura Asset URL The Eptura Asset URL is generated during onboarding. e.g. https://mycompany.managerpluscloud.com/lt/module/assets/b0d68775-ebea-4c67-8aa8-3d1a7c3e7387 |
Onboard to Tandem |