The difficult part of a PI ProcessBook migration is rarely the display file. It is the years of VBA, writeback, navigation, analysis, and operator shortcuts embedded in it. This guide shows how to move the supported display foundation to AVEVA PI Vision and use Vision Library+ where an operational workflow still needs more.
AVEVA has retired PI ProcessBook and positions AVEVA PI Vision as the path forward. AVEVA's migration utility can analyze ProcessBook displays and convert supported content into native, editable PI Vision displays. That solves an important part of the move—but it does not remove the need to understand what each display actually does for its users.
The real legacy
Why companies still depend on PI ProcessBook
Many ProcessBook estates are not simply collections of trends and values. Over time, engineers and operators added VBA macros, custom buttons, writeback forms, navigation rules, calculations, external links, and display-specific shortcuts. Those additions often became part of the operating procedure—even when nobody formally documented them.
The display may be old. The workflow is not.
A macro that looks like a small technical customization may be how an operator records a laboratory result, selects a production line, opens a related display, starts an investigation, or compares a batch with its reference run.
This is why a visually successful conversion can still fail operationally. The screen may appear in PI Vision while the interaction people relied on has disappeared.
Hidden business logic
VBA may contain calculations, validations, naming rules, or dependencies that are not visible in the display itself.
Operator muscle memory
Buttons and shortcuts can be deeply embedded in daily rounds, shift handovers, troubleshooting, and reporting.
Unclear ownership
The original author may be gone, while the display remains critical and its code has never been formally tested or documented.
The migration foundation
Use the official utility for the display—then assess the workflow
The PI ProcessBook to PI Vision Migration Utility provides the right baseline. AVEVA explains that migrated displays become native and editable in PI Vision, and supported ProcessBook datasets can become PI Vision calculations. That preserves more of the original investment than rebuilding every screen from zero.
What the utility is designed to move
- Supported display elements and their visual structure
- PI data references and compatible configuration
- Supported datasets as editable PI Vision calculations
- A display that can continue to be edited in PI Vision
What still needs explicit analysis
- VBA-driven user interactions and automation
- Writeback, validation, and approval behavior
- Custom navigation and context switching
- External integrations or display-specific business rules
Important: Vision Library+ provides supported, configurable PI Vision symbols and controls that can replace many common workflow patterns without recreating every macro as new custom code. For display-specific VBA, such as custom graphics, colour logic, calculations or set-point buttons, Custom Visualization+ lets an AI chat rewrite the macro as a PI Vision visualization. See how to convert ProcessBook VBA with AI.
From code to capability
Translate each VBA routine into the job it performs
The most useful migration inventory is not a list of macro names. It is a list of user outcomes. For every VBA routine, record who uses it, what starts it, which data it reads or writes, what result the user expects, and what happens when it fails.
Some routines will disappear because PI Vision already provides the required capability. Some can be replaced with a configurable Vision Library+ control. Others—especially integrations with external systems or highly specific business logic—may still require separate engineering. Treat that distinction as a design decision, not a migration failure.
Vision Library+ migration patterns
Map familiar ProcessBook workflows to maintainable PI Vision building blocks
Vision Library+ extends PI Vision with interactive dashboarding, data entry, Event Frame tools, navigation, analysis, alarms, and display controls. The goal is not to imitate ProcessBook pixel for pixel. It is to give users a clearer, supportable way to complete the same operational job.
| ProcessBook or VBA pattern | Operational need | Possible PI Vision pattern | Migration question |
|---|---|---|---|
| Custom navigation buttons | Move between related displays while preserving asset or time context | Navigation Menu+, Navigation Button+, Asset Select+, DateTime Picker+ | Which context must travel with the user? |
| Manual entry or writeback forms | Record readings, lab values, notes, reason codes, or corrections | Manual Data Entry+, Manual Input Table+, Quick Input+, Manual Input Form+ | Which values may be written, by whom, and with what validation? |
| Ad hoc trend popups | Investigate a value without rebuilding the display | Value+, Combo Chart+, DateTime Picker+ | Which data and default time range should open? |
| SPC, SQC, and custom analysis | Review distribution, variation, limits, and operating periods | Combo Chart+, Histogram+, Box Plot+, Period Comparison Chart+ | Is the result exploratory, operational, or part of a validated calculation? |
| Batch or downtime macros | Find, filter, compare, and investigate Event Frames | Events Table+, Event Gantt Chart+, Event Filter+, Event Comparison Chart+, Playback Tool+ | What defines the event set and the comparison window? |
| Alarm and attention logic | Make active conditions visible and support operator response | Alarm Table+, Alarm Sound+, Value+, Linear Gauge+, Radial Gauge+ | Which state requires attention, acknowledgement, or escalation? |
| Embedded context and supporting data | Show AF data, tables, or related web content beside the process view | SQL Table+, Time Series Table+, Asset Comparison Table+, WebView+ | Is the source read-only, interactive, or governed by another system? |
| Display-specific VBA graphics, logic and buttons | Keep the custom view, calculation or set-point button of one display | Custom Visualization+, with the VBA rewritten by an AI chat (conversion guide) | Does the macro stay inside the display, or does it reach files, databases or other applications? |
A controlled path forward
A six-step ProcessBook migration plan
Build the display inventory
List PDI and PIW files, owners, users, data sources, usage frequency, criticality, and known VBA or add-in dependencies.
Classify the VBA
Group routines by navigation, data entry, calculation, visualization, integration, administration, or obsolete behavior.
Convert the supported baseline
Use the official migration utility and review its analysis output before accepting the converted display.
Map the remaining gaps
Choose native PI Vision first, Vision Library+ where a supported extension fits, and custom engineering only where the requirement is genuinely unique.
Pilot a representative workflow
Select a display with real complexity: navigation, writeback, analysis, and operator interaction—not only a simple trend screen.
Validate and scale
Test with the people who use the display, document accepted patterns, and then apply those patterns across the wider estate.
Migration acceptance
Validate the workflow, not only the screenshot
A side-by-side image comparison cannot confirm that a migration is complete. The acceptance test must include the decisions and actions the display supports.
DataThe correct PI points, AF attributes, calculations, Event Frames, and time contexts are used.
InteractionNavigation, filtering, asset selection, popups, and user inputs behave as expected.
WritebackPermissions, validation, timestamps, and failure messages are appropriate for the workflow.
PerformanceThe display remains usable with realistic data volumes, user concurrency, and refresh behavior.
OperationsOperators can complete the normal, abnormal, and handover scenarios they previously handled.
SupportabilityThe new pattern has an owner, documentation, version information, and a clear support route.
Frequently asked questions
PI ProcessBook migration FAQ
Does the PI ProcessBook to PI Vision Migration Utility convert VBA?
The utility provides the baseline display migration, but VBA-driven behavior should be inventoried and handled as a separate workflow requirement. Some outcomes can use native PI Vision features or Vision Library+ controls. Display-specific macros can be rewritten by an AI chat as a Custom Visualization+ document, and integrations with other systems may still need custom engineering.
Is Vision Library+ a replacement for PI Vision?
No. Vision Library+ extends AVEVA PI Vision. Its symbols and controls are configured alongside native PI Vision elements, PI points, AF attributes, calculations, and Event Frames.
Can Vision Library+ replace every ProcessBook macro?
No single product can promise a one-to-one replacement for arbitrary VBA. Vision Library+ covers many recurring dashboard and workflow patterns, such as navigation, data entry, analysis, Event Frame work and alarms. For the display-specific rest, Custom Visualization+ runs AI-converted macros inside the display, while macros that reach files, databases or other applications still need a separate solution.
Which ProcessBook display should we migrate first?
Choose a representative display that matters to users and contains several common challenges. A pilot with navigation, calculations, writeback, and interaction provides a more useful migration pattern than starting with the simplest screen.
Should we keep the original ProcessBook files?
Keep a controlled archive of the original files, dependency inventory, screenshots, VBA source, and acceptance results according to your organization's retention and governance requirements. The archive is useful for traceability even after users move to PI Vision.
Bring one representative display
Map your ProcessBook workflow to a maintainable PI Vision design
Show us the display and the behaviors your users rely on. We can help separate what the official migration covers, what Vision Library+ can replace, and what still requires a project-specific solution.
