ProcessBook modernization guide
Moving from PI ProcessBook to PI Vision is a chance to modernize how teams view, share, and operate PI System data—not simply replace one display tool with another.
ProcessBook displays may contain years of operational knowledge, so a successful migration needs more than a software installation. It needs an inventory of what people rely on, a plan for what should be rebuilt, and a validation cycle that proves the new PI Vision displays support the same decisions with a better long-term workflow.
ProcessBook and PI Vision solve different problems
PI ProcessBook is a desktop-oriented visualization environment that many teams used to assemble interactive process displays. Those displays often encode important context: operator conventions, engineering limits, shift routines, and the tags people check during an event.
PI Vision provides a browser-based experience for exploring PI System data through responsive displays and asset context. The move changes how displays are accessed, shared, maintained, and extended. It also creates an opportunity to simplify layouts that became difficult to maintain over time.
Access from the browser
Users can open displays through a web application instead of distributing a desktop client and managing local display files.
Use context more effectively
Asset Framework context, collections, and reusable display patterns make it easier to compare similar equipment and scale a monitoring workflow.
Build a modern extension path
PI Vision supports browser-based extensions and custom symbols, including the richer dashboards and controls available through Vision Library+.
Why organizations make the transition
Make displays easier to reach
A browser-based display can be shared through a controlled URL and opened from the workstations or devices approved for the role.
Reduce duplicate maintenance
Reusable display patterns and asset context can reduce the need to maintain a separate copy of the same visual logic for every unit or area.
Improve collaboration
Teams can work from a common web display and standardize the views used by operations, engineering, maintenance, and management.
Extend the workflow
Custom symbols can add focused capabilities for tables, data entry, annotation, reporting, heatmaps, and other workflows that were difficult to provide in a legacy desktop display.
Assess your ProcessBook estate before rebuilding
Do not start by converting every display in the order it was created. Start by understanding which displays are still used, who owns them, what data they depend on, and which interactions are essential to the job.
| Inventory question | Why it matters | Decision |
|---|---|---|
| Who uses the display? | Usage and role determine access, layout, and validation needs. | Retain, redesign, or retire |
| Which data sources are used? | Tags, AF elements, calculations, and event context must be mapped. | Recreate and test dependencies |
| Which interactions matter? | Navigation, time-range changes, selections, and annotations may not map one-to-one. | Redesign the operator path |
| Is the display still accurate? | Migration is a good time to remove unused symbols and stale limits. | Clean before rebuilding |
| Does it need an extension? | Some workflows need a custom symbol or a different PI Vision pattern. | Choose the supported approach |
Prioritize by operational value: migrate the displays that support daily decisions, alarms, production reviews, or troubleshooting first. A smaller validated set is more useful than a large untested conversion.
Plan the migration in controlled stages
Map the source display
Capture the ProcessBook display, its tags, calculations, navigation, scripts, annotations, and the user tasks it supports.
Choose the PI Vision design
Decide whether the best result is a direct visual recreation, a cleaner asset-context display, or a redesigned workflow with fewer but more useful interactions.
Build and configure
Recreate the display with PI Vision symbols, apply the right AF context, and add custom symbols only when they solve a defined operational need.
Validate with users
Ask the people who used the original display to perform real tasks. Confirm that the new view makes the same decision possible and that important context is still visible.
Publish with ownership
Assign an owner, record dependencies, document permissions, and define how future changes will be reviewed and tested.
Handle features that do not migrate directly
A ProcessBook display may include VBA macros, embedded objects, local files, or other desktop assumptions. Treat these as requirements to analyze rather than features to copy blindly. In PI Vision, the equivalent may be a standard symbol, an Asset Framework pattern, a browser workflow, or a supported custom symbol.
Desktop scripts
Document the business outcome of every script first. Then determine whether a standard PI Vision interaction, automation, or custom extension is appropriate.
Static navigation
Replace repeated links and copied displays with asset context, collections, folders, and a clear navigation model where that improves maintainability.
Specialized visuals
Use a supported custom symbol when a workflow needs more than the standard palette. Keep configuration, ownership, and update requirements documented.
For a practical example of the migration workflow, see How to migrate a ProcessBook display to PI Vision. Test every extension in the target PI Vision version before using it in production.
Validate the new display before users depend on it
Data correctness
- Compare representative values and timestamps.
- Check units, quality, time ranges, and calculations.
- Test empty, bad-quality, and unavailable data.
Operator usability
- Repeat the real task the ProcessBook display supported.
- Confirm that navigation and selections are obvious.
- Check the display on approved desktop and mobile widths.
Administration
- Verify access, ownership, and display publishing rules.
- Document AF and symbol dependencies.
- Record the validation result and rollback path.
The strongest migrations preserve the operational intent while removing unnecessary technical baggage. A PI Vision display should be easier to open, understand, update, and extend than the ProcessBook display it replaces.
Start with the displays that matter
Turn your ProcessBook inventory into a prioritized PI Vision migration plan with clear owners, tests, and upgrade decisions.
View the migration workflow
