Release Version: BetaRelease VersionBeta Vendor Support: Official Integration: Free To Automate


Setup Instructions

1. Prerequisites

  1. Grant IMSURGE Agent Access
    • Log into your iTwin IoT project and navigate to Users and Roles.
    • Add the service account service-LqaqMInpOh69L2ofbWdMHuNNv@apps.imsoidc.bentley.com.
    • Assign the IoT Creator role.
  2. Create a Data Source Connection
    • In your iTwin IoT project, go to the Connections tab.
    • Create a Data Source API Import connection. This will display a Connection ID in the form /api/XXXXX/node.

2. Creating the Integration

The IMSURGE integration setup screen will prompt you for the following details.

  • Project ID – the UUID from the project URL (e.g. https://itwiniot.bentley.com/71b7138c-a99f-4187-8140-f12de7acd15e).
  • Connection ID – the API endpoint of the Data Source connection you created (e.g. /api/4A7B32/node).

Concerns & Limitations

  • Pipeline-based configuration – iTwin IoT device and sensor definitions are saved on the pipeline. Deleting a pipeline removes its associated devices and sensors.
    If you want to run multiple pipelines to the same iTwin IoT device or sensors with different polling rates, use the Clone/Duplicate feature to copy a pipeline and adjust the polling rate on the clone. This can be useful for workflows such as having an hourly instrument sync alongside a nightly 24-hour backfill to capture out-of-order data from instruments that occasionally go offline.
  • Metadata support – metadata, specifically unit of measure, may not always map directly to a known instrument definition in iTwin IoT. If known metric values are required for instrument data imported via IMSURGE, sensors can be mapped to known definitions using iTwin IoT’s calculator feature. For further assistance regarding usage of the calculator feature, contact iTwin IoT support.

Reference


External References