Skip to main content
Data Management
PI System
Configuration

How to Omit PI Point Prefix in the PI Connector for UFL

Learn how to omit PI Point prefixes in the PI Connector for UFL to streamline your data management. This guide provides detailed steps for configuration adjustments.

Roshan Soni

4 min read

How to Omit PI Point Prefix in the PI Connector for UFL

When working with the OSIsoft PI Systems, data point names often include prefixes to help categorize and organize them effectively. However, there might be situations where you prefer to streamline your data organization by omitting these prefixes. Specifically, if you're using the PI Connector for Universal File and Stream Loading (UFL), you may want to know if it's possible to omit the PI Point prefix.

In this blog post, we will explore how to customize the PI Connector for UFL to omit the PI Point prefix.

Why Omit the PI Point Prefix?

In a PI System, prefixes are generally used for ease of categorization, helping users immediately recognize the source of data points. But there are instances where you might want your point names to be as concise as possible or to fit an existing naming convention more closely. Removing the prefix can aid in:

  • Simplifying point names.
  • Reducing redundancy when the prefix does not add meaningful context.
  • Matching the format of existing systems where prefixes are not used.

The Quick Solution

The PI Connector for UFL allows for significant customization without altering the foundational setup of your PI System. Here’s how you can omit the prefix for PI Points:

  1. Locate the Configuration File: First, navigate to the configuration directory for the PI Connector for UFL:

    • C:\Program Files\PIPC\Connectors\UFL\Configuration\
  2. Edit the Prefix Configuration: Open the configuration file named PIPointPrefix.config.json, which defines point prefixes:

    {
      "PIPointPrefix": "UFL"
    }
    
  3. Update the Prefix Value: Change the value of the PIPointPrefix. Set it to an empty string ("") to omit the prefix.

    {
      "PIPointPrefix": ""
    }
    
  4. Apply Changes for New PI Points Only: It's critical to understand that this change only affects newly created PI Points. Existing PI Points that already contain the prefix must be adjusted manually.

  5. Renaming Existing PI Points: To rename existing points:

    • Stop the connector service to prevent data collection during the renaming process.
    • Manually rename the existing PI Points to remove the prefix.
    • Restart the connector service to resume data collection without prefixes.

Precautions

  • Back Up Configuration Files: Always back up configuration files before making changes to avoid accidental data loss.
  • Impact on Existing Data: Consider how renaming might affect historical data or integrations with other systems.
  • Coordinate with Team/IT Management: If working within a larger team, make sure all relevant parties are aware of the changes to prevent confusion.

Conclusion

Omitting the PI Point prefix in your PI Connector for UFL configuration is straightforward and can lead to more streamlined data management. By following the steps outlined, you can effectively remove prefixes from new data streams while planning adequately for existing data points.

Tags

#PI Connector for UFL
#PI Point Prefix
#Data Organization

About Roshan Soni

Expert in PI System implementation, industrial automation, and data management. Passionate about helping organizations maximize the value of their process data through innovative solutions and best practices.

Sign in to comment

Join the conversation by signing in to your account.

Comments (0)

No comments yet

Be the first to share your thoughts on this article.

Related Articles

Enhancing PI ProcessBook Trends with Banding and Zones: User Needs, Workarounds, and the Road Ahead

A look at the user demand for trend banding/zoning in OSIsoft PI ProcessBook, current VBA workarounds, UI challenges, and how future PI Vision releases aim to address these visualization needs.

Roshan Soni

Migrating PIAdvCalcFilVal Uptime Calculations from PI DataLink to PI OLEDB

Learn how to translate PI DataLink's PIAdvCalcFilVal advanced calculations—like counting uptime based on conditions—into efficient PI OLEDB SQL queries. Explore three practical approaches using PIAVG, PIINTERP, and PICOunt tables, and get tips for validation and accuracy.

Roshan Soni

Understanding PI Web API WebID Encoding: Can You Generate WebIDs Client-Side?

Curious about how PI Web API generates WebIDs and whether you can encode them client-side using GUIDs or paths? This article explores the encoding mechanisms, current documentation, and best practices for handling WebIDs in your applications.

Roshan Soni