AVEVA PI Vision visualization guide
Combo Charts in AVEVA PI Vision: A Practical Design Guide
Use bars, lines, areas, and scatter series together when one operational question depends on several related signals. The goal is not to add more data—it is to make the comparison easier to read and verify.
A standard trend works well when every series has a similar role. It becomes harder to read when a team needs to compare a period total, a changing process value, a target, and event context in the same time window. Combo Chart+ extends PI Vision with configurable bars, lines, areas, scatter plots, multiple Y-axes, limit overlays, and Event Frame context for that type of analysis.
Start with the decision the display must support. Then give each measure one clear visual role and remove anything that does not help the reader make that decision.
Choose each series by the job it performs
Chart types are not interchangeable decoration. Bars emphasize magnitude by category or period, lines emphasize change and continuity, areas add range or accumulation context, and scatter points expose the relationship between paired values.
| Series | Use it for | Configuration check |
|---|---|---|
| Bars | Production totals, batch counts, downtime minutes, or other discrete comparisons. | Use a meaningful order, label the aggregation period, and keep a consistent baseline when height is compared. |
| Lines | Targets, setpoints, limits, and continuously changing process values. | State whether the line is measured, calculated, or a reference and show its unit. |
| Areas | Operating ranges, accumulated values, or background context behind a foreground trace. | Use restrained opacity so the area does not obscure bars, markers, or limit lines. |
| Scatter | Relationships between paired variables such as quality result versus process condition. | Confirm that the paired values share a meaningful time or sample relationship. |
Keep the axes honest
Combo Chart+ supports multiple configurable Y-axes, which is useful when related series have different units or ranges. Each additional axis also increases the chance that a reader will compare shapes that only look similar because their scales were chosen independently.
Use one axis when possible
Series with the same unit and comparable range are easiest to interpret on one scale. This keeps slopes, gaps, and thresholds visually consistent.
Add an axis for a real unit difference
Use a second scale when the comparison is operationally meaningful, such as hourly production beside process temperature. Label the unit, color association, range, and direction clearly.

Build the chart around one operational question
Suppose a production team wants to know whether output is meeting the hourly target and whether shortfalls coincide with a process condition. A practical view could use bars for hourly output, a line for the target, and a second line or area for the process variable.
Decision test: can the reader identify the target gap, the corresponding process state, and the relevant time window without changing displays or decoding an oversized legend?

Add overlays only when they change the investigation
Limits and targets
Use multistate limit lines to show a defined operating boundary, target, or statistical reference. Make the source and meaning of the value explicit.
Event Frames
Overlay Event Frames when an operator needs to connect a process change with a downtime event, batch, excursion, or other recorded interval.
Selected-range statistics
Use on-demand minimum, maximum, and average values to summarize a selected interval, then confirm that the selected time range is the one being discussed.
These features are most useful when they reduce context switching. If an overlay does not alter the investigation or the next action, leave it out of the primary display.
Validate the display before operational use
A chart can render correctly and still communicate the wrong relationship. Review the data, configuration, and interpretation with the process owner before making it part of an operator workflow.
- Confirm every PI Point or Asset Framework attribute, unit, calculation, and aggregation period.
- Test normal, boundary, missing, stale, and out-of-range values.
- Change the time range and asset context to verify that all series respond as expected.
- Check that targets, limits, Event Frames, and statistics use documented sources and definitions.
- Review the chart at the actual display size; legends, axes, markers, and tooltips must remain readable.
- Ask a second engineer to explain the conclusion without guidance. If the interpretation differs, simplify or relabel the view.
Common design failures
Too many scales
Independent axes can make unrelated shapes appear correlated. Use the fewest scales needed and expose every unit.
Decorative series
Every bar, line, area, point, and overlay should answer part of the operational question. Move supporting detail to another view.
Hidden time assumptions
Totals, averages, and events must use a clearly understood time basis. Similar-looking series may represent different intervals.
