54660 FAQ: FactoryTalk Historian ProcessBook and FactoryTalk Hist...

1 of 2

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/54660

Rockwell Automation Support Center

54660 - FAQ: FactoryTalk Historian ProcessBook and FactoryTalk Historian
ActiveView
Access Level: Everyone
Date Created: 08/26/2008 12:07 PM
Last Updated: 01/15/2015 10:04 PM

FactoryTalk ProcessBook is a feature-rich graphical interface to the FactoryTalk Historian that allows you to create both individual display files (.pdi) and/or collections of
displays in a workbook file (.piw). In addition to displays, a ProcessBook Workbook can also include other entries:
links to other ProcessBook workbook files
links to other ProcessBook displays
operating system commands
FactoryTalk Historian ActiveView (also known as 'ProcessBook Client for View/VantagePoint') is an ActiveX control for viewing ProcessBook displays that have been
published to a web server. ActiveView facilitates viewing displays in any ActiveX container, such as Internet Explorer, FactoryTalk View Site Edition or FactoryTalk
VantagePoint. ActiveView can only be used with ProcessBook displays, it does not support the other entries contained within a ProcessBook workbook (listed above).
Typically, ProcessBook is used to develop and test displays for web publishing and ActiveView is used as the client to view published displays. However, ProcessBook itself can
also be used as a client.

Frequently Asked Questions:

I'm new to FactoryTalk Historian Site Edition, but familiar with FactoryTalk View Site Edition (Network). In the context of developing and deploying projects, are
there any similarities between the 2 products?
Yes.
Both systems are client-server based architectures and both are typically distributed across several host computers.
ProcessBook is somewhat analogous to View Studio, because you use it to develop and test your displays.
A ProcessBook workbook is somewhat analogous to a View SE project, because it is a collection of related items. However, a ProcessBook workbook is only 1 file (.piw),
whereas a View SE project is a folder that contains many other sub-folders and files.
A ProcessBook display is (.pdi) analogous to a View SE display (.gfx), because it can contain graphics, animation and numeric displays.
ActiveView is somewhat analogous to the View SE Client, because it is used to view completed displays. However, ActiveView is an ActiveX control (as opposed to an
application like the View SE Client).
Why does ProcessBook allows me to create both individual display files (.pdi) and workbooks (.piw) that can also contain additional links? Why would I choose
one vs. the other?
The client you plan to deploy typically determines which option you choose. Individual displays are typically intended for use with ActiveView clients, while workbooks are
generally intended for ProcessBook clients.
I've already started my project using a workbook file (.PIW), but I want to utilize ActiveView clients - have I made a big mistake?
Not at all. ActiveView can only be used with individual display files (.PDI), however, it includes a special display named Export.pdi to extract the individual displays from the
workbook file. See the ActiveView User's Guide or the online help for more information.
I've already started my project using individual displays, but I want to utilize ProcessBook clients - have I made a big mistake?
No, but you may want to convert to a workbook file to make things easier for your clients. Within the workbook, you'll now have a 'Table of Contents" where you can link to the
individual displays. If you prefer make the displays "native" (vs. using links) you must convert them.
Is there a utility to accomplish this conversion (or import) of individual displays into a single workbook - like there is for the export?
No. You also cannot use File > Import from within ProcessBook for this purpose. Rather, the procedure is as follows:
Open the existing .pdi
Select all components in the .pdi
Copy components from the .pdi
Create a new .piw (or open an existing one)
Create a new display in the .piw
Paste Components from .pid into the .piw
Save the .piw Note: If the display contains VBA, this may require additional modifications to the VBA code.
Does FactoryTalk ProcessBook have any Add-ins?
Yes. The available Add-ins are BatchView and SQC. For more information, refer to the ordering information link (below). Note: In August 2014, OSIsoft introduced the AF
Display Builder Add-in for ProcessBook. Rockwell Automation does not currently support AF Display Builder with FactoryTalk ProcessBook.
Does FactoryTalk ActiveView work with FactoryTalk View Site Edition (Local) or FactoryTalk View Machine Edition?
No. For more information see FactoryTalk Historian SE requires a Network FactoryTalk Directory. However, with the release of FactoryTalk View SE v7.00, there is another
option. For more information, refer to 534697 - FAQ: FactoryTalk Historian and FactoryTalk View Site Edition v7.00 (CPR 9 SR 6).
Does FactoryTalk ActiveView work with OSI PI?
No (unlike FactoryTalk DataLink and FactoryTalk ProcessBook).
When using the ActiveView ActiveX control within a View Only FactoryTalk View Site Edition (Network) client, can I still interact with the ActiveX?
Yes and No. You will be able to interact with trends and navigate to other PB displays, but you will not be able to write values back to the controller.
Where can I find ordering information for these products?http://www.rockwellautomation.com/rockwellsoftware/data/historian/orderinginfo.html
Where can download updates for these products?
The Rockwell Software Updates site: http://www.rockwellautomation.com/support/webupdates/

19/3/2015 1:29 PM

54660 FAQ: FactoryTalk Historian ProcessBook and FactoryTalk Hist...

2 of 2

https://rockwellautomation.custhelp.com/app/answers/detail/a_id/54660

For more information, see the FactoryTalk Historian ProcessBook and FactoryTalk Historian ActiveView User's Guides or online help.

Comments (0)
This answer has no comments

Post a Comment

Product Tree for This Answer (expand/collapse)

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects.
Accordingly, the information in this web site is not intended to constitute application, design, software or other professional engineering advice or services. Before making any
decision or taking any action, which might affect your equipment, you should consult a qualified professional advisor.
ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED IN THIS WEB SITE AND
MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO
USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.
ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION (INCLUDING SOFTWARE)
PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. Note that
certain jurisdictions do not countenance the exclusion of implied warranties; thus, this disclaimer may not apply to you.

This page is best viewed in Internet Explorer 10, Firefox 31, Chrome 37, Safari 6 or newer.

19/3/2015 1:29 PM