Home › Technical articles

Đọc bằng tiếng Việt

PI ProcessBook to PI Vision migration: what the Migration Utility moves, what it leaves behind, how to plan

TDL Industrial Automation · Last updated:

From AVEVA's 2021 blog, the PI ProcessBook to PI Vision Migration Utility 2020 documentation and PI Vision 2026: why ProcessBook is retired, what PI Vision changes (web server, SQL database, PI AF identity permissions), the three analysis results, what does not move (VBA, ActiveX, OLE, SQC chart, layers), the migration steps and a plant plan.

PI ProcessBook is the PI System's desktop display tool, a thick client installed on each user's PC, whose process graphics and trends are saved as .PDI files. In a blog post dated 20 October 2021, AVEVA announced that it is retiring PI ProcessBook and named AVEVA PI Vision, its web-based display tool, as the replacement. AVEVA documents a PI ProcessBook to PI Vision Migration Utility that analyses .PDI files and moves what it can into PI Vision displays. This article follows that utility's documentation (the 2020 release) and the PI Vision 2026 documentation, the newest PI Vision set on docs.aveva.com. Where PI Vision sits in a PI System: What is AVEVA.

PI ProcessBook to PI Vision: what the Migration Utility movesFive layers from top to bottom. PI ProcessBook: thick client, .PDI and .PIW files saved in PI ProcessBook 3.0.15.7 or later; displays hold symbols, trends, buttons, VBA code, ActiveX controls and OLE objects. Through Add Files and Run Analysis to the Migration Utility: each display is classed Can be fully migrated, Can be partially migrated (for example with VBA) or Cannot be migrated (file cannot be analysed); reports are the analysis as .csv, the migration as HTML and Export VBA as a .vba file. Select displays and Migrate, to Migration Settings: server address webServer/PIVision, destination folder, owner, PI AF identities with Read or Write access; displays linked by buttons must be migrated together; option to migrate PI Calculation data sets. Displays are created on the PI Vision server: application server on IIS, SQL database holding the display definitions; buttons become gray rectangles with navigation links, Arial font, no layers; not migrated: VBA code, ActiveX controls, OLE objects, SQC chart, BatchView. Symbols read data from the PI AF server and Data Archive; element relative displays need the PI AF connection during migration; multi-state limits are correct only with a connection; users open displays in a browser. Based on AVEVA PI ProcessBook to PI Vision Migration Utility 2020 and PI Vision 2026 documentation.PI ProcessBook to PI Vision: what the Migration Utility movesPI ProcessBookthick client, .PDI and .PIW filesdisplays saved in PI ProcessBook 3.0.15.7 or latersymbols, trends, buttons, VBA code,ActiveX controls, OLE objectsAdd Files, Run AnalysisMigration UtilityanalysisCan be fully migrated · everything movesCan be partially migrated · some parts stay behind, forexample VBACannot be migrated · the file cannot be analysedreports: analysis .csv, migration HTML, Export VBA to .vbaselect displays, MigrateMigration Settingsbefore the moveserver as webServer/PIVision, destination folder, ownerPI AF identities with Read or Write accessdisplays linked by buttons: migrate them togetheroption: migrate PI Calculation data setsdisplays created on the PI Vision serverPI Vision displayapplication server andSQL databasebuttons become gray rectangles with navigation linksArial font, no layersnot migrated: VBA code, ActiveX controls, OLE objects,SQC chart, BatchViewsymbols read dataData sourcesPI AF server and Data Archiveelement relative displays need the PI AF connectionduring migrationmulti-state limits are correct only with a connectionusers open displays in a browserBased on AVEVA, PI ProcessBook to PI Vision Migration Utility 2020 documentation (target PI Vision 2020) andPI Vision 2026 documentation (read 22 November 2026). Figure: drawn by TDL.
Figure 1: PI ProcessBook to PI Vision: what the Migration Utility moves. On a phone, swipe sideways to see the whole figure.

1. Why AVEVA is retiring PI ProcessBook

The blog gives two reasons. First, in AVEVA's words, "the existing code base is outdated compared to the new products we offer". Second, security: PI Vision does not rely on outdated technology, which matters in regulated plants. Retiring ProcessBook also lets AVEVA's engineers focus on the software it plans to support for decades. The blog names PI Vision 2020 as the path forward for ProcessBook users.

The blog gives no end-of-support date. AVEVA's Knowledge Base article 000105219 (customer support portal, last updated 20/08/2026) lists PI ProcessBook among the PI System products whose End of Sale and End of Life have both elapsed, with an End of Support Date of 31/12/2024: it no longer receives technical support and the download is no longer available.

2. What changes with PI Vision

PI Vision is not a program on each PC. In PI Vision 2026 (version 3.12.0) it is a web application with these parts:

Part What the PI Vision 2026 documentation says
Clients most modern browsers, including tablets and phones on iOS or Android; tested with Edge, Chrome, Firefox and Safari; Internet Explorer 11 is no longer supported
Application server runs on Microsoft IIS, Windows Server 2019 to 2025 and .NET Framework 4.8; handles all application operations between clients and Data Archive, PI AF and SQL Server
Websites the application at webServer/PIVision/ over HTTPS, administration at webServer/PIVision/Admin; small devices are redirected to /PIVision/m
SQL database stores display definitions: name, owner, symbols, permissions; SQL Server 2017 or later, Azure SQL or Amazon RDS for SQL Server
PI Server supported and tested with PI Server 2018 and later (Data Archive 3.4.420, PI AF 2.10); an older PI AF loses some functions
Authentication Windows authentication, OpenID Connect or both in a domain; OpenID Connect only in a workgroup

Users who search Data Archive or PI AF need PI mappings; a PI trust is not enough for search. AVEVA recommends putting the PI Vision database on the same SQL Server as PI AF when both are on premises, so one backup routine covers both.

The utility's feature comparison lists what each tool has. PI ProcessBook is a thick client; PI Vision runs on a central application server. Both have process graphics, trends, display security, Asset Framework support, multi-state, asset switching, data export and client-side calculations. Only PI Vision has mobile use, event frames, symbol collections and drill-in navigation, and it supports notifications where ProcessBook stops at PI Notifications 2012 and earlier. Only ProcessBook has SQC; in PI Vision it needs a custom extensibility symbol.

Access works differently too. PI Vision grants display and folder permissions to PI AF identities, at four levels:

Permission What the identity's users can do
Read view the display and save a copy
Write edit and save the display
Manage change permissions, rename, move and delete the display
Custom adjust inherited permissions or deny a permission explicitly

On top of that, each user has an access level: Administrators, Publishers (save and share displays), Explorers (view and export data, no saving) and Utility Users, who may connect the PI Vision Display Utility, the migration utility or the public REST API. Without PI AF identities, the Windows groups PI Vision Admins, PI Vision Users and PI Vision Utility Users do the same job.

3. What the Migration Utility reads and reports

The utility analyses .PDI and .PIW files saved in PI ProcessBook 3.0.15.7 or later, and its documentation names PI Vision 2020 as the target. It installs on Windows 8.1, Windows 10 and Windows Server 2012 to 2019. The PI Vision 2026 security pages still list it among the tools that Utility Users may connect, but neither documentation set states that the 2020 utility supports PI Vision 2026 as a target; confirm the utility version for your PI Vision release with AVEVA before planning the move.

After analysis, each display falls in one of three groups:

  • Can be fully migrated. Everything moves, though formatting can look slightly different.
  • Can be partially migrated. One or more parts cannot move; the Issues column shows which.
  • Cannot be migrated. The utility cannot analyse the file, for example one last saved in an older ProcessBook version.

Three reports come out: the analysis as a .csv file, the migration as HTML, and the VBA code as a .vba file. AVEVA says the migrated displays match their sources as closely as possible in size, position and colour, and stay editable in PI Vision.

4. What does not move

The documented limits, for PI Vision 2020 as the target:

Item What happens
VBA not supported in PI Vision; the display moves without its code; the display is flagged partially migrated
Control (ActiveX) not supported in modern browsers; not migrated
OLE object, SQC chart, BatchView no PI Vision equivalent; not migrated
Button becomes a gray rectangle with its text and a navigation link; links to unsupported applications or actions, or to displays the utility cannot resolve, are dropped
Layers not preserved
Fonts everything becomes Arial; bold, italic and underline are lost
Symbol visibility hiding a symbol is possible only as a multi-state behaviour
Unit conversion AF attributes show the units set on the attribute
Number formats %, absolute value and some custom formats are replaced by the same number of decimals
Trends, XY plots some legend, scale and axis options are lost; logarithmic scales and regression lines display differently; partial or relative timestamps are not supported
Element relative displays the utility must reach the PI AF server, or the asset context may migrate incorrectly
Multi-state limits correct only with a connection to Data Archive or PI AF; limits on PI Calculation data sets always give a warning

The symbol library in PI Vision is an updated version, so some ProcessBook library symbols do not exist there and others look different.

5. The steps the documentation gives

  1. Select Add Files, browse folders or files and tick the displays to analyse.
  2. Select Run Analysis and read the Summary or Tree View; filter by status or issue.
  3. For displays with a VBA flag, select Export VBA and review the .vba file. Older ProcessBook versions may need the VBA Install Kit from the AVEVA Support portal.
  4. Select the fully or partially migratable displays and select Migrate.
  5. In Migration Settings, enter the PI Vision server address (HTTPS, host webServer, path /PIVision), choose the destination folder, the display owner and the PI AF identities with Read or Write access.
  6. Choose what happens to duplicate names (Skip by default, or Overwrite), whether to keep the ProcessBook folder structure, and whether to migrate PI Calculation data sets.
  7. Select OK; the displays are created on the PI Vision server.

Displays linked by buttons must be migrated in the same operation, or their links may stop working. If a display holds an image larger than 2 MB, the default ImageFileSize limit, PI Vision cannot create it; AVEVA shows how to raise the limit in the dbo.Settings table of the PI Vision database and then recycle the application pools.

6. Planning the move in a plant

The documentation points to a few things that belong in the plan:

  • Inventory first. The analysis run over all .PDI folders gives the list, and the .csv report opens in Excel.
  • PI AF before migration. Element relative displays and multi-state limits need live connections, and when PI Calculation data sets are not migrated, the documentation points to calculations in PI AF or in PI Vision instead. Displays for assets built from one AF template can be reused through the asset list or an ?Asset= URL parameter, so one display can serve every asset of the same type. How to model those templates: PI Asset Framework.
  • Test, then production. The PI Vision Display Utility copies displays from a test server to a production server and can point them to new data sources. In PI Vision 2026 it needs a trusted TLS certificate on the server.
  • Permissions as a design task. PI AF identities, folders and the four access levels decide who sees what, so map them before the first display is published.

Keeping PI ProcessBook running beside PI Vision until users accept the new displays is not something the documentation prescribes; it is a choice each plant makes.

What we check first

This is TDL's practice, not an AVEVA requirement.

  • How many .PDI and .PIW files exist, where they live, and which ones people still open.
  • Which displays carry VBA, ActiveX controls or OLE objects, and what that code actually does for the operator.
  • The PI Server, PI AF and Data Archive versions, and whether PI Vision is already installed and on which version.
  • Whether the assets on the main displays already exist in PI AF as templates and elements.
  • PI AF identities and mappings for each user group, and who will be Publisher, Explorer or Utility User.
  • Buttons that link displays together, so linked sets are migrated in one pass, and images larger than 2 MB.
  • Data that looks wrong after migration goes to the interface and buffering first: PI System troubleshooting.

How TDL approaches it

TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem. With ProcessBook displays we start from the people who use them: which screens they open every shift, and which calculations or scripts they rely on, before any file is converted. Background: What is a process historian, AVEVA Historian vs PI System, AVEVA Historian retrieval modes, AVEVA system integrator in Vietnam and SCADA, HMI and plant data integration.

Frequently asked questions

Is PI ProcessBook still supported?

AVEVA announced in October 2021 that it is retiring PI ProcessBook and replacing it with PI Vision. AVEVA Knowledge Base article 000105219 gives its End of Support Date as 31/12/2024; technical support and downloads have ended.

Does VBA code in PI ProcessBook displays move to PI Vision?

No. PI Vision displays do not support VBA. The utility migrates the display without its code and flags it as partially migrated; Export VBA saves the code to a .vba file for review.

Which ProcessBook files can the Migration Utility read?

.PDI and .PIW files from PI ProcessBook 3.0.15.7 or later. Files it cannot analyse, for example ones last saved in an older version, are listed as cannot be migrated.

Do users need to install anything to open PI Vision displays?

No. PI Vision runs on an application server and users open it in a browser: Edge, Chrome, Firefox or Safari, including on iOS and Android devices. Internet Explorer 11 is no longer supported.

Does PI Vision need PI AF?

PI Vision reads data from Data Archive or PI AF and grants display permissions to PI AF identities. For migration, element relative displays need a connection to the PI AF server, and an AF server older than PI AF 2018 loses some PI Vision functions.

Sources

Read 22 November 2026. Apart from one short quoted phrase from the AVEVA blog, this article paraphrases the sources; read the original documents before designing or working on a system.

Related services:
SCADA & historian AVEVA (Wonderware)