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

CONNECT EAP

TABLE OF CONTENTS

PI bulk import

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedOct 30, 2026
  • 2 minute read

A PI bulk import copies existing PI Server archive data to CONNECT. It is designed to import large volumes of historical data, such as a year of data or more, before transitioning to continuous data streaming using the PI to CONNECT agent.

The PI Archive files must cover the historical range to import. The archive files used for the PI bulk import should already be stored as part of routine archive and backup maintenance. The import uses a customer-owned classic Azure file share as an intermediate staging location.

The PI bulk import involves three people working together:

  • Azure account holder:

    • Provisions or configures the file share.

    • Assigns the required roles to the PI Server administrator or other designated uploader.

    • Generates the SAS URL.

    • Hands the file share URL and SAS token to the CONNECT operator.

  • PI Server administrator:

    • Stages the archive files for the selected historical range.

    • Generates the metadata files by using the PIConfig script.

    • Uploads the archive files and generated metadata files to Azure.

    • Coordinates with the CONNECT operator or administrator to install and configure the PI to CONNECT agent for continuous data streaming.

  • CONNECT operator:

    • Creates and monitors the PI bulk import.

    • Notifies the PI Server administrator when the import completes successfully and Coordinates with the PI Server administrator to install and configure the PI to CONNECT agent for continuous data streaming.

After the PI bulk import is complete, transition to PI to CONNECT ongoing updates by installing and configuring a PI to CONNECT agent on the PI Server. The CONNECT operator or administrator and the PI Server administrator typically work together on this task, although either role can complete it with the required access and permissions.

To execute this process successfully end to end, follow the PI bulk import workflow. It breaks down each required step to import historical PI data into CONNECT, identifies the person responsible for performing each task, and provides detailed instructions and prerequisites for each subtask.