Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

CONNECT EAP

TABLE OF CONTENTS

Create and monitor PI bulk import

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedNov 03, 2026
  • 4 minute read

Completed by: CONNECT operator

Create and start a PI bulk import in CONNECT to import PI tags and event data (known as data points in CONNECT) from Azure. The import is designed to move large volumes of PI data and can be bandwidth intensive.

A successful import populates the target CONNECT data store with the selected historical PI data. You can expect the following results:

  • A stream is created for each imported PI point.

  • Stream types are created to represent the data shape of the related PI point types.

  • Historical events from the selected PI Archive files are imported into the corresponding streams.

    Note: Digital sets are not imported into CONNECT as stream types. For digital events, CONNECT stores both the integer value and the string value as part of the event.

Prerequisites

  • Access to the CONNECT portal, including:

    • The target CONNECT site has been created. CONNECT automatically creates an associated data store when the site is created.

    • Access to read and write to the target CONNECT site/data store.

    • Access to create and manage PI bulk imports (a role like Account Administrator, Account Contributor, or Data Manager).

  • The Azure file share URL and SAS token from the Azure account holder who completed Generate Azure file share SAS URL for PI bulk import.

To create a PI bulk import

  1. Log in to your CONNECT account.

  2. From the navigation rail, select Data connections and then choose the Bulk import tab.

  3. Select Create new transfer.

    The Bulk data import wizard opens.

  4. From Add import name, enter an Import name and select Next.

  5. Select a target destination for the import.

    For either destination, it is recommend that the target CONNECT data store be in the same geography as the Azure storage account containing the file share. Check the storage account's geography and region provided by the Azure account holder before selecting your destination.

    To select the data store associated with the target CONNECT site (recommended):

    1. Select Single real-world site.

    2. From the Site dropdown, select the target site. CONNECT imports the data into the data store associated with that site.

    3. Select Next.

    To import data into a staging area instead (you can assign them to a site later):

    1. Select Multiple real-world sites.

    2. From the Staging area dropdown, select a staging area.

    3. Select Next.

      After the import, review the stream assignment instructions and assign any unassigned streams.

  6. From Configure data import, enter the Azure storage location URL and SAS token provided by your Azure account holder as one combined value:

    https://<StorageAccountName>.file.core.windows.net/<FileShareName>?<SasToken>

    Note: The SAS token expires 7 days after Azure issues it. The token must still be valid when you start or restart the import.

    CONNECT validates the SAS URL and token when the import starts. If required parameters are missing or the SAS token has expired, the import cannot start. Contact the Azure account holder to generate a replacement SAS URL and token, and then enter the updated combined value.

    Then select Next.

  7. From Review, verify the import details. When you are ready to begin, select Create.

    The import is created, but does not start immediately. You must manually start the import when you are ready.

    Note: A PI bulk import can take up to one week to complete, depending on data volume and import conditions. Monitor import progress regularly during this period.

  8. When you are ready to start the import, select the Start link for the import.

    The import begins, and you can monitor its progress.

  9. Notify the PI Server administrator can transition to synchronizing live data using a PI to CONNECT agent as described in Handoff to the PI Server administrator below.

Monitor and verify the import

Monitor progress while CONNECT builds stream types and streams and populates the target data store with historical data.

Import status

While the PI bulk import is in progress, you can monitor its status from the Bulk Import tab on the Data connections page. Detailed import status, including the number of archives processed, is displayed in the side sheet when your import is selected.

If an error occurs during the import, the import status indicates the error and provides a link to view details.

Statuses include:

  • Not started

  • Initializing

  • Importing

  • Canceling

  • Canceled

  • Completing

  • Completed

  • Completed with errors

  • Failing

  • Failed

Failed imports

If an import fails, contact AVEVA Support for assistance with repairing and resuming the existing import. Creating a replacement import and starting over is not recommended.

SAS token validity

The SAS token is valid for 7 days after Azure issues it. CONNECT validates and uses the token when the import starts. After the import starts, the token can expire without interrupting the import because CONNECT does not use it again during uninterrupted processing.

If the token expires before you start the import, or if you need to restart a long-running import after the token expires, ask the Azure account holder to complete Generate Azure file share SAS URL for PI bulk import again. Enter the new SAS URL and token, and then start or restart the import.

Upon successful completion of the import

You can confirm that the import completed successfully in the following ways:

  • The import displays a status of Completed, which confirms the import completed successfully. The number of archives processed is displayed.

  • The target data store now includes new streams and stream types for the imported data.

  • If the imported streams do not have an assigned site, you must associate them with a site later. For instructions on this topic, see Assign streams to site.

Logging

To review the detailed outcome of an import, access its logs from the Logs page. Filter Service type to display logs for Bulk Ingress. Download the log as a CSV file for further analysis.

For more information, see Logs.

Handoff to the PI Server administrator

After the import completes, coordinate the installation and configuration of a PI to CONNECT agent with the PI Server administrator. This task is typically completed jointly by the CONNECT operator or administrator and the PI Server administrator, but either role can complete it with the required access and permissions. The agent keeps the target data store synchronized with ongoing updates from the PI Server.

For more information on the PI to CONNECT agent and how to install it, see:

In This Topic