PI bulk import workflow

To complete a PI bulk import of historical PI data into CONNECT, complete this workflow from start to finish. The Azure account holder first configures the customer-owned Azure file share environment. The PI Server administrator then prepares the PI Archive files on the server where they are located and stages them in the file share. Right before PI bulk import creation, the Azure account holder runs a script to generate a SAS URL for the customer-owned Azure file share. Each linked subtask includes the full implementation details for that step, including the prerequisites that must be in place before you begin it. Complete each subtask in order, and do not skip any steps.Participants and responsibilities

Before you begin

• Create the target CONNECT site before starting this workflow, if it does not already exist. CONNECT automatically creates an associated data store when the site is created. For more information, see Create your first site.

• Confirm the target data store's geography and region with the CONNECT operator so the Azure account holder can configure the file share in a suitable location.

Participants and responsibilities

PI bulk import is typically completed by multiple people. Use these role definitions to identify ownership for each workflow step and to coordinate handoffs.

• 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.

The CONNECT operator or administrator and the PI Server administrator typically work together to install and configure the PI to CONNECT agent for ongoing updates. Either role can complete this task if they have the required access and permissions.

Workflow

The diagram and steps below map the process of completing a PI bulk import. The numbered actions in the diagram align directly to the numbered steps in this workflow, while unnumbered actions represent actions that CONNECT performs as part of internal processing that occurs between user actions. You do not need to perform any action for those unnumbered system steps.

Bulk import diagram

1. Configure Azure file share prerequisites

   Complete the Azure account holder setup tasks required before PI script execution. Before creating or selecting the storage account, confirm the target data store's geography with the CONNECT operator. We recommend using the same geography. Successful completion provides an Azure Storage account resource within your Azure subscription, a file share contained within that Storage account for the PI bulk import, and the permissions the PI Server administrator or another designated uploader needs to stage the PI Archive files. Completed by Azure account holder.

2. Prepare and stage PI Server migration files

   On the server where the PI Archive files are located, identify the files in the archive folders that cover the selected historical range. Save and run the metadata script in a writable folder on that same server; the generated CSV files are saved there. Collect the archive files and generated CSV files in a local staging folder on that server or another server with access to the files, and upload them to the prepared Azure file share. Completed by PI Server administrator.

3. Generate Azure file share SAS URL for PI bulk import

   Create the PowerShell script from the linked topic, and run it to generate a 7-day, read-only Shared Access Signature (SAS) URL for an Azure file share in your organization's Azure subscription. Completed by Azure account holder.

4. Create and monitor PI bulk import

   Create, start, monitor, and verify the PI bulk import in CONNECT. Completed by CONNECT operator.

5. Transition to PI to CONNECT agent for continuous data streaming

   After the import, install and configure PI to CONNECT to transition to continuous data streaming. Completed by CONNECT operator or administrator, PI Server administrator, or both, typically working together.