Skip to content
Software AthleteSoftware Athlete
The Benefits of Using Custom Symbols in AVEVA PI Vision

The Benefits of Using Custom Symbols in AVEVA PI Vision

Custom symbols for AVEVA PI Vision

The benefits of using custom symbols in AVEVA PI Vision

Use custom symbols when the standard PI Vision views do not show the context, interaction, or comparison your team needs to work with PI data.

Audience: PI administrators, process engineers, and dashboard owners   Focus: visualization, context, interaction, and maintainability

Light AVEVA PI Vision custom-symbol workflow with chart, context table, and controlled interaction panels
Custom symbols extend a PI Vision display when a standard symbol does not fit the operational question.

Standard PI Vision symbols are a good starting point for trends, values, tables, and basic dashboards. The limitation appears when the display must do more than show one value or one trend: compare a fleet, keep event context beside the process data, enter an approved observation, or guide a user through related displays.

A custom symbol adds value when it removes one of those gaps inside PI Vision. The benefit is not visual novelty. It is a clearer path from the data to the task the user needs to complete.

Standard symbols are the foundation; custom symbols fill specific gaps

Use standard symbols when they fit

  • Trends, values, tables, and basic status views already answer the question.
  • The workflow does not need extra interaction or a different data relationship.
  • The team wants the smallest possible display surface to maintain.

Use a custom symbol when the workflow needs more

  • The display must compare assets, events, attributes, or other related values in one view.
  • Users need a focused action such as filtering, navigation, data entry, or export.
  • Keeping the context in PI Vision avoids a separate manual step or disconnected tool.

This is not an either-or decision. Keep the standard symbols that work, and add an extension only where it gives the user a concrete improvement.

Four benefits users can see in the workflow

1

See comparisons clearly

Purpose-built charts and tables can compare assets, attributes, limits, or trends in a layout that matches the question. This helps users spot differences without opening separate displays for every item.

2

Keep context beside the data

Event, asset, hierarchy, and reference information can sit next to the value it explains. Users can investigate the condition without losing the process view.

3

Support the next action

Filters, navigation controls, exports, and controlled data-entry forms can expose the action the workflow requires instead of relying on an informal sequence of clicks.

4

Make displays easier to reuse

A documented symbol with a repeatable configuration can be used across assets or units. That is easier to govern than a collection of one-off workarounds copied from display to display.

Examples of custom-symbol workflows

The best symbol depends on the task. These examples show how the benefit changes with the user’s question.

Workflow problem Useful extension End-user benefit
Operators need event context while reviewing process data. Events Table+ Review event records beside the display instead of switching to a separate event search.
Engineers need several asset attributes in one comparison. SQL Table+ Inspect hierarchy and related values in a structured table that can support filtering or export.
Authorized users need to enter a process observation or setpoint. Manual Data Entry+ or Quick Input+ Keep the write-back step close to the process context, with the permissions and validation required by the environment.
Users need to compare multiple assets or performance measures. Comparison charts and tables in the Vision Library+ collection Rank, filter, and investigate a peer group without building a separate page for each asset.

What the user gains from the right extension

The right custom symbol should make a specific PI Vision task easier to complete. Vision Library+ groups the useful extensions around the work users need to do: capture data, understand performance, operate a dashboard, and investigate Event Frames.

1

Data entry in the display

Record manual readings, lab results, comments, reason codes, or shift notes while the asset, time range, and related process data remain visible. The user can complete the input step in the same context instead of switching to a separate form or spreadsheet.

  • Keep the write-back step beside the process view.
  • Use focused fields for supported PI values and attributes.
  • Connect the entered value to the relevant asset, batch, or timestamp.
Quick Input+ manual data-entry custom symbol in PI Vision

Manual Data Entry+ and Quick Input+ support focused data-entry workflows.

2

Advanced charts and visualization

Go beyond a single trend or value. Combo Chart+ can combine lines, bars, areas, or scatter plots on one chart, helping engineers compare values, show different scales, overlay limits or Event Frames, and inspect the detail behind a change.

  • Compare operating areas, assets, attributes, or periods.
  • Present related data in the visual form that fits the question.
  • Move from a summary to the supporting asset context.
Combo Chart+ showing line and bar series together in AVEVA PI Vision

Vision Library+ includes comparison, chart, KPI, table, and analysis extensions.

3

Dashboard-like features inside PI Vision

Display-wide filters, asset and time selectors, KPI cards, navigation, linked views, and other controls turn a static display into an operational workspace. Users can filter, analyze, drill down, and act without losing the PI Vision context.

  • Reuse one display across assets, shifts, or operating periods.
  • Keep selected filters and context aligned across the view.
  • Move to a related display or detail view without starting over.
Vision Library+ custom symbols collection displayed in an AVEVA PI Vision dashboard

The goal is a useful sequence: filter the view, analyze the result, drill down, and take the next action.

4

Event Frame management

Review batches, downtime, excursions, and other Event Frames with tables, timelines, filters, KPIs, comparisons, analytics, and playback in the same PI Vision workflow. This gives users a way to move from “what happened?” to “why?” while the surrounding process data stays available.

  • Find and filter the Event Frames relevant to the investigation.
  • Compare duration, categories, losses, or event windows.
  • Open the related trend or detail view without losing the event context.
Events Table+ custom symbol showing structured Event Frame context in PI Vision

Events Table+ is one part of the Vision Library+ Event Frame workflow.

Keep the benefit measurable. Before deploying a custom symbol, define what should improve for the end user:

  • fewer display changes to find the needed context;
  • faster recognition of an outlier or exception;
  • fewer repeated manual steps; or
  • a clearer, verifiable path to the next action.

Start with the workflow, then choose the symbols

Do not start with a symbol catalog. Start with the problem the user is trying to solve. Once the workflow is clear, choose the smallest combination of native PI Vision elements and custom symbols that supports each step.

1

Identify the problem

What is difficult today? Is the user missing event history, comparing assets, entering a reading, or moving between related displays?

2

Describe the workflow

Write down who uses the display, which PI Points, AF attributes, or Event Frames are involved, what the user needs to see, and what should happen next.

3

Choose the symbol combination

Combine the pieces that match the workflow: for example, an asset or time selector with a comparison chart, an Event Filter+ with an Events Table+, or data-entry controls beside the relevant trend.

4

Validate the complete display

Test the full path with real data, empty selections, bad quality, permission limits, and the browsers used by your team. Confirm that the user can complete the intended task without losing context.

Common questions

Do custom symbols replace standard PI Vision symbols?

No. Standard symbols remain the right choice when they answer the question. Custom symbols extend the display only where the workflow needs a different visualization, interaction, or context model.

Do custom symbols make every dashboard better?

No. Adding a symbol without a clear user task can make a display harder to read and maintain. Choose an extension when it solves a specific gap and test whether users can complete the intended task more directly.

What should administrators verify before rollout?

Verify the symbol version, data sources, permissions, browser support, API or backend dependencies, error states, and the process for updating the display when the PI Vision environment changes.

Find the right extension for your PI Vision workflow

Vision Library+ provides a documented collection of custom symbols for visualization, context, interaction, data entry, events, and navigation in AVEVA PI Vision. Use the Vision Library+ documentation for installation and configuration details.

Explore Vision Library+Read the documentation
1 comment on The Benefits of Using Custom Symbols in AVEVA PI Vision
  • prabhat
    prabhat

    can you use pi vision custom symbol to trend data from an external data source like an api or SQL database

    November 22, 2025
Leave a comment

Your email address will not be published..

Cart 0

Your cart is currently empty.

Start Shopping