Skip to content
Software AthleteSoftware Athlete
Top 5 Custom Symbol Extensions Every PI Vision User Should Know

Vision Library+ selection guide

Top 5 Custom Symbol Extensions Every PI Vision User Should Know

These five extensions address common PI Vision gaps: controlled manual input, mixed-chart analysis, relational context, audible alarms, and consistent display navigation.

Updated August 28, 2026 · Originally published October 9, 2024 · Reviewed by Software Athlete PI Vision engineering

AVEVA PI Vision already covers core trending and display workflows. Custom symbols are useful when a team has a specific operational task that the standard symbol set does not handle. The best starting point is therefore the repeated workaround—not the longest feature list.

The five choices below are all part of Vision Library+. Each solves a different problem, so the recommendation is to pilot the one that removes the clearest bottleneck first.

Operational task Recommended symbol Use it when
Record manual values Manual Data Entry+ Operators or laboratory teams need controlled, validated time-series input.
Compare unlike variables Combo Chart+ Lines, bars, areas, scatter data, or multiple scales belong in one analysis.
Add relational context SQL Table+ AF or SQL-backed reference data must sit beside process data.
Make a condition audible Alarm Sound+ A visual threshold also needs a configurable sound and mute state.
Standardize display access Navigation Menu+ Users need a consistent path through many PI Vision displays.

1 · Data entry

Manual Data Entry+ for operator and laboratory values

Manual Data Entry+ gives authorized users a grid for entering and reviewing values for PI Points or AF attributes from a PI Vision display. It fits operator rounds, laboratory results, shift notes, and temporary manual collection when an automated source is unavailable.

The symbol supports multiple targets, validation, spreadsheet copy and paste, CSV import, timestamps, and an audit trail. That makes it a better fit than a single-value control when users must enter several related observations together.

Pilot check
  • Confirm the intended users have write permission only for the approved targets.
  • Test numeric, string, Boolean, and enumeration inputs that the workflow actually uses.
  • Write a known test value and verify its timestamp, quality, and audit record before rollout.
Manual Data Entry+ grid for entering PI Point and AF attribute values in PI Vision
Manual Data Entry+ is the first choice when a workflow needs several validated values in one controlled grid.

2 · Analysis

Combo Chart+ for mixed chart types and scales

Combo Chart+ combines lines, bars, areas, and scatter plots in one visualization. Multiple Y-axes help compare variables with different units or ranges, while Event Frame overlays and selectable statistics add context to the same time window.

Choose it when the engineering question depends on a relationship—for example production versus target, energy use across utilities, or a process value against control limits. Keep the number of traces deliberate: a combined view only helps when operators can still identify each scale and series.

Pilot check
  • Assign the correct unit and Y-axis to every series.
  • Test the relevant PI Vision time ranges and any Event Frame overlay.
  • Ask a representative user to identify the expected relationship without explanation.
Combo Chart+ combining line and bar series in an AVEVA PI Vision display
Use mixed chart types when the relationship between variables matters more than a separate chart for each signal.

3 · Relational context

SQL Table+ for AF and SQL-backed tables

SQL Table+ displays AF Tables—including tables linked to SQL and other sources—inside PI Vision. Filtering, sorting, multistate formatting, time-range filtering, import, export, and supported editing workflows turn reference data into part of the operational display.

It is useful for laboratory context, shift logbooks, production targets, maintenance records, or configuration data that does not belong in a time-series trend. Use a read-only configuration when display users only need context; enable editing only where ownership and permissions are clear.

Pilot check
  • Verify the AF Table or linked source returns the expected rows for the display context.
  • Apply filters and conditional formatting only where they clarify a decision.
  • If editing is enabled, test create, update, and delete behavior with a non-production record.
SQL Table+ showing structured AF and SQL-backed information inside PI Vision
SQL Table+ keeps structured reference or relational data beside the process information it explains.

4 · Operator awareness

Alarm Sound+ for audible PI Vision conditions

Alarm Sound+ plays a configured sound when a value meets the defined condition. Its visual state distinguishes normal, active, and muted behavior, and an operator can mute the sound from the symbol.

Use it as an additional PI Vision notification layer, not as a substitute for the site's governed alarm-management or safety system. A sound should correspond to a condition the operator understands, with an agreed response and a way to avoid nuisance alarms.

Pilot check
  • Test the threshold, sound, browser audio behavior, active state, and mute control.
  • Verify that repeated or changing conditions behave as the operating procedure expects.
  • Document what the operator should do after the alert is heard.
Alarm Sound+ showing an active visual alarm state in PI Vision
Audible feedback is useful only when the triggering condition, mute behavior, and operator response are defined.

Roll out one workflow before adding five symbols

The safest adoption path is a small, measurable pilot. Use the same sequence whether the first target is data entry, analysis, context, alarm awareness, or navigation.

  1. Define the bottleneck: write down the current workaround, responsible role, and expected result.
  2. Confirm prerequisites: check the PI Vision environment, data sources, PI Web API access, and user permissions relevant to the selected symbol.
  3. Build a test display: configure one representative use case with real naming, units, limits, and navigation targets.
  4. Verify with an operator or engineer: test the expected action and at least one failure or edge condition.
  5. Document ownership: record who maintains the configuration and how changes will be validated.

Installation and symbol-specific configuration guidance is available in the Vision Library+ documentation.

Common questions

PI Vision custom symbol FAQ

Which custom symbol should a team implement first?

Start with the repeated workaround that has a clear owner and a result you can verify. Manual Data Entry+ is a strong first pilot for structured manual values; Navigation Menu+ is often the better first step when users struggle to find the correct display.

Do these extensions replace standard PI Vision symbols?

No. Standard symbols remain appropriate for core visualization. Add a custom symbol when the workflow requires data entry, mixed analytical views, relational context, audible behavior, or navigation that the standard set does not provide.

Are all five symbols included in Vision Library+?

Yes. The current product pages list Manual Data Entry+, Combo Chart+, SQL Table+, Alarm Sound+, and Navigation Menu+ as part of Vision Library+.

Leave a comment

Your email address will not be published..

Cart 0

Your cart is currently empty.

Start Shopping