SW HOTT #1 Student Manual - 12-19-08

STUDENT MANUAL FACTORYTALK HOTT #1
Contact Rockwell Automation

Customer Support Telephone 1.440.646.3434
Online Support http://support.rockwellautomation.com
Copyright Notice
2007 Rockwell Automation Technologies, Inc. All rights reserved. Printed in USA.
2007 OSISoft, Inc. All rights reserved.
This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation
Technologies, Inc. Anyreproduction and/or distribution without prior written consent from Rockwell Automation
Technologies, Inc. is strictly prohibited. Please refer to the license agreement for details.
Trademark Notices
FactoryTalk, Rockwell Automation, Rockwell Software, the Rockwell Software logo are registered trademarks of
Rockwell Automation,Inc.
The following logos and products are trademarks of Rockwell Automation, Inc.:
FactoryTalk Historian Site Edition (SE), RSView, FactoryTalk View, RSView Studio, FactoryTalk View Studio,
RSView Machine Edition, RSView ME Station, RSLinx Enterprise, FactoryTalk Services Platform, and FactoryTalk
Live Data.
The following logos and products are trademarks of OSIsoft, Inc.:
PI System, Sequencia, Sigmafine, gRecipe, sRecipe, and RLINK.
Other Trademarks
ActiveX, Microsoft, Microsoft Access, SQL Server, Visual Basic, Visual C++, Visual SourceSafe, Windows,
Windows ME, Windows NT, Windows 2000, Windows Server 2003, and Windows XP are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
ControlNet is a registered trademark of ControlNet International.
DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA).
Ethernet is a registered trademark of Digital Equipment Corporation, Intel, and Xerox Corporation.
OLE for Process Control (OPC) is a registered trademark of the OPC Foundation.
Oracle, SQL*Net, and SQL*Plus are registered trademarks of Oracle Corporation.
All other trademarks are the property of their respective holders and are hereby acknowledged.
Restricted Rights Legend
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii)
of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013
Warranty
This product is warranted in accordance with the product license. The products performance may be affected by
system configuration, the application being performed, operator control, maintenance, and other related factors.
Rockwell Automation is not responsible for these intervening factors. The instructions in this document do not cover
all the details or variations in the equipment, procedure, or process described, nor do they provide directions for
meeting every possible contingency during installation, operation, or maintenance.
This products implementation may vary among users.
This document is current as of the time of release of the product; however, the accompanying software may have
changed since the release. Rockwell Automation, Inc. reserves the right to change any information contained in this
document or the software at anytime without prior notice. It is your responsibility to obtain the most current
information available from Rockwell when installing or using this product.
2008 Rockwell Automation, Inc. All rights reserved.
Rev. 121908
CONTENTS:
Lesson 1
Installing FactoryTalk Historian (Version 2.1)
Lesson 2
Using Discover Historian Points (Version 2.1)
Lesson 3
Understanding Historian Tags and Using Excel Tag

Configurator
Lesson 4
Using Data Collection Modes of Polled vs. Advised
Lesson 5
Buffering Distributed FTLD Interface Data
Lesson 6
Understanding and Using Exception and

Compression
Lesson 7
Configuring Performance Equations
Lesson 8
Configuring Totalizers
Lesson 9
Configuring Event Trigger Reads
Lesson 10
Configuring Basic Output Points
Lesson 11
Using Data Collection With Handshaking
Lesson 12
Understanding and Using Basic Alarms
Lesson 13
Configuring Event Framing-BaGen
Lesson 14
Using BatchView
Lesson 15
Working with Digital States
Lesson 16
Using FTLD Health Points
Lesson 17
Using and Displaying Audit Information
Lesson 18
Using Archive Management Tools
Lesson 19
Scheduling Backups of Historian Data
Lesson 20
Configuring Interface Redundancy
Lesson 21
Using View SE Updated Trend Object to Display

Historian Data
Creating and Editing ProcessBook Trends
Using Dynamic Elements in ProcessBook
Inserting ProcessBook Displays in View SE Via
ActiveView
Using ProcessBook Data Sets
Using ProcessBook Relative Displays
Lesson 22
Lesson 23
Lesson 24
Lesson 25
Lesson 26
Rev. 121908
Lesson 27
Lesson 28
Lesson 29
Lesson 30
Lesson 31
Lesson 32
Lesson 33
Lesson 34
Lesson 35
Appendix A
Appendix B
Appendix C
Appendix D
Appendix E
Configuring and Using ProcessBook SQC

Using DataLink Sampled vs. Compressed Data
Using DataLink Archived Data and Digital Tags
Inserting DataLink Trend Objects
Using DataLink Filtered Compressed Function
Using DataLink Calculated Data Function
Using DataLink Time Filtered Function
Utilizing ACE - Unit Conversions
Using Reporting Services
Installing Activation and FactoryTalk Services
Platform
Creating a FactoryTalk Application
FactoryTalk Historian Time Function
Rev. 121908
Lesson 1
What You Will Learn
1. How to install the components of FactoryTalk Historian

utilizing a distributed data collection interface node.
These components you will install include:
FactoryTalk Historian Server
FactoryTalk Historian Distributed Interface
Visualization Applications
FactoryTalk Historian SE
FactoryTalk Historian SE is a scalable and integrated solution. It redefines the options for
manufacturers who want to maximize their ability to collect and analyze process data. Use
FactoryTalk Historian to capture data across your enterprise while serving the data to plant
applications. This allows for fast and reliable data capture at the controller level and at high
speeds and low intervals.
Historians are utilized across many industries and applications:

Consumer Products, Food and Beverage, Automotive, Life Sciences
Continuous Process, Packaging, Material Routing
Key benefits of a Historian:
Capture and process high-speed, time-series data
Store in a central (Site or Enterprise) data repository for future analysis
Historical data is used for:
Analysis through calculations, statistical processes, quality controls
Supports business and operational analysis:
Trends and graphs of data
Rev. 121908
Lesson 1 Installing FactoryTalk Historian (Version 2.1)
Page 2
Rev. 121908
Page 3
FactoryTalk Historian SE provides the capability to collect, store, analyze, and visualize data
using a powerful engine and a set of reporting tools such as time-series trends, bar charts,
piecharts, pareto and tabular trends, and an easy method of generating reports using Microsoft
Excel. It also uses compressed storage data algorithms to contain a vast amount of data in a small
format. You can retrieve data spanning a long or short time span quickly. FactoryTalk Historian
SE is closely integrated with the following Rockwell Automations FactoryTalk Services
Platform and Applications.
FactoryTalk LiveData (FTLD): A direct data interface to FactoryTalk LiveData delivers

native FTLD data directly to Historian without requiring intermediate interfaces and
standards such as OPC.
FactoryTalk Directory: FactoryTalk Historian uses FactoryTalk Directory to look up data

points for configuring points to historize. The directory is also used for auto-discovering
controller data sources and tags in the initial configuration process.
FactoryTalk Security: By integrating FactoryTalk Historian with FactoryTalk Security,

all users and user groups can be maintained centrally, and a single sign-on is fully
supported.
FactoryTalk Activation: FactoryTalk Historian is activated by Rockwell Automation's

central licensing system based on the FactoryTalk Activation Server.
FactoryTalk Diagnostics: Because of FactoryTalk Historian's close integration with

FactoryTalk Diagnostics, all system and diagnostics messages from FactoryTalk
Historian are centrally stored and maintained in the FactoryTalk central Diagnostics
database.
FactoryTalk Audit: All FactoryTalk Historian server auditing messages are stored and
available in the FactoryTalk central Audit database.
FactoryTalk View SE Trending: FactoryTalk View Supervisory Edition natively trends

data from FactoryTalk Historian.
Ordering Information
FactoryTalk Historian Servers include:
Data point-limited license (either FactoryTalk Live Data or 3rd Party)
One single-user FactoryTalk Historian DataLink (Excel Add-In) license
One RSLinx Enterprise license
FactoryTalk Adminstration Console
Updated TrendX object for FactoryTalk View SE to display FactoryTalk Historian data
FactoryTalk Historian servers ship with FactoryTalk Activation, and do not include an activation
diskette. Instructions for activating software via the Internet are included. FactoryTalk Historian
Rev. 121908
Page 4
server licenses are additive. For example, if 1400 Reporting Tags are required, purchasing and
installing both a 500 and 1000 Reporting Tags license on a single server will activate as a 1500
Reporting Tags server.
Server connections are separated in two types: one for connecting to Rockwell Automation data
sources, primarily through FactoryTalk Live Data, and one for connecting to third-party data
sources using OPC or any of the 450 native connectors for the historian.
Catalog Number
9518-HSERA500
9518-HSERA1K
9518-HSERA2K5
9518-HSERA5K
9518-HSERA10K
9518-HSERA20K
9518-HSERA50K
9518-HSERA100K
Description
FactoryTalk Historian Site Edition 500 Live Data Tags
FactoryTalk Historian Site Edition 1,000 Live Data Tags
Catalog Number
9518-HSE3RD500
9518-HSE3RD1K
9518-HSE3RD2K5
9518-HSE3RD5K
9518-HSE3RD10K
9518-HSE3RD20K
9518-HSE3RD50K
Description
FactoryTalk Historian Site Edition 500 Third Party Data Tags
FactoryTalk Historian Site Edition 1,000 Third Party Data Tags
Third-Party Historian Interfaces

Communication to third-party devices can either be through FactoryTalk Live Data using a
third-party OPC server (purchased separately) configured as a FactoryTalk Live Data server or
through one of the third-party Historian interfaces listed below.
Catalog Number
Description
9518-HINOPCAE
Historian Interface for OPC Alarm and Events media only
9518-HINOPCHDA Historian Interface for OPC HDA media only
9518-HINOPCXML Historian Interface for OPC XML plug-in media only
9518-HINRELDB
Historian Interface for ODBC media only
9518-HINDDE
Historian Interface for DDE media only
9518-HINFTP
Historian Interface for FTP media only
9518-HINTCP
Historian Interface for TCP Response media only
9518-HINTRACE
Historian Interface for Trace Route Response media only
9518-HINHTML
Historian Interface for HTML media only
9518-HINXML
Historian Interface for XML media only
9518-HINXMLHTTP Historian Interface for HTTP XML media only
9518-HINXMLFILE Historian Interface for File Reader XML plug-in media only
9518-HINBATFILE Historian Interface for Batch Files media only
Rev. 121908
Page 5
9518-HINUNIFILE Historian Interface for Universal File Loader media only

9518-HINWINEVT Historian Interface for MS Windows Event File media only
9518-HINDNP3
Historian Interface for DNP 3.0 media only
9518-HINFFT
Historian Interface for Fourier Transformations media only
9518-HINPERFMON Historian Interface for Historian Perfrmance Monitor media only
9518-HINEPLC
Historian Interface for Modbus Ethernet media only
9518-HINMPLC
Historian Interface for Modbus/Modbus Plus PLC media only
9518-HINABBIMS Historian Interface for ABB IMS Advant media only
9518-HINABBPDL Historian Interface for ABB IMS Advant PDL media only
9518-HINABBPBS Historian Interface for ABB Procontrol P for PBS media only
9518-HINCITECH Historian Interface for Citech media only
9518-HINFOXBORO Historian Interface for Foxboro AW70 Series - media only
9518-HINGECIMPL Historian Interface for GE Cimplicity media only
9518-HINGEEPIC Historian Interface for GE EPIC media only
9518-HINGEPAC4K Historian Interface for GE PAC 4010/4020 media only
9518-HINHONPHD Historian Interface for Honeywell PHD media only
9518-HINHONSC3K Historian Interface for Honeywell Scan3000 media only
9518-HINSIEMPCS Historian Interface for Siemens PCS media only
9518-HINSIEMS5 Historian Interface for Siemens Simatec Net S5 media only
9518-HINSIEMS7 Historian Interface for Siemens Simatec Net S7 media only
9518-HINASPEN
Historian Interface for AspenTech CIM-IO Client media only
9518-HINIFIX
Historian Interface for Intellution FIX (FIX32/iFIX) media only
9518-HININTOUCH Historian Interface for Wonderware InTouch media only
Authoring Client
The FactoryTalk Historian Authoring Client licenses allow a user, using either the FactoryTalk
Historian DataLink Client, to develop Microsoft Excel reports, or the FactoryTalk Historian
ProcessBook Client, to develop graphical analytics to either stand alone or to be integrated into
FactoryTalk View screens. Purchase one Authoring Client license for each user who will be
performing FactoryTalk Historian authoring functions.
Catalog Number
9518-HPBENE
9518-HPBENF
9518-HDLENE
9518-HDLENF
Description
FactoryTalk Historian ProcessBook Authoring Client Single User
FactoryTalk Historian ProcessBook Authoring Client Concurrent
FactoryTalk Historian DataLink Excel Reporting tool Single User
FactoryTalk Historian DataLink Excel Reporting tool - Concurrent
FactoryTalk Historian ProcessBook Client License for View SE

The FactoryTalk Historian ProcessBook Client license for View SE allows users to view
FactoryTalk Historian ProcessBook displays within FactoryTalk View SE displays. Purchase a
Single-User Runtime Client license for each user who will access the system concurrently.
Catalog Number
9518-HCLNTENF
Description
FactoryTalk Historian ProcessBook Client License for View SE
Rev. 121908
Page 6
FactoryTalk Historian Integration with FactoryTalk Batch

The FactoryTalk Historian EVT interface allows the historian to capture FactoryTalk Batch
events from the FactoryTalk Batch Journal or Event log file. As the events are written to the
journal by FactoryTalk Batch, the historian is picking up those events, and adding them to the
FactoryTalk Historian Batch Database. These events can then be visualized as event frames on
top of the time-series data.
The BatchView add-in can be used to visualize these events in either ProcessBook displays or in
Excel.
Catalog Number
9518-HINEVT1U
9518-HINEVT3U
9518-HINEVT10U
9518-HINEVT30U
9518-HINEVT60U
9518HBAVENE
9518HBAVENF
Description
EVT interface to FactoryTalk Batch 1 unit
BatchView add-in for FactoryTalk Batch Database single user
BatchView add-in for FactoryTalk Batch Database concurrent license
System Requirements
The hardware and software required with FactoryTalk Historian Site Edition depends on the
demands an application places on the system. The greater the demand, the more powerful a
system is required. For large or complex applications, use computers with faster CPUs and more
RAM. In any application, faster CPUs and more RAM will result in better performance. In
addition, there should always be sufficient disk space to provide virtual memory that is at least
twice the size of the physical RAM.
Windows 2000 Operating System

If you are using a Windows 2000 operating system, MDAC 2.7 or above must be installed
before FactoryTalk Historian can be installed.
FactoryTalk Historian Site Edition 25,000 Points and Below
Minimum: Intel Pentium D, 3.2Ghz, 1GB RAM
Operating Systems:
Microsoft Windows 2003 Server with Service Pack 1 or later
Microsoft Windows XP Professional with Service Pack 2 (Recommended for testing
purposes only)
Rev. 121908
Page 7

Minimum: Intel Pentium Xeon, 3.0Ghz, 2GB RAM
Operating Systems:
Microsoft Windows 2000 Server with Service Pack 4 or
purposes only)
Minimum: Intel Pentium Xeon dual processor, 3.4Ghz, 4GB RAM
Operating Systems:
purposes only)
FactoryTalk Historian Site Edition Interface Node
Minimum: Intel Celeron D, 3.0Ghz, 512MB RAM
Operating Systems:
Microsoft Windows XP Professional with Service Pack 2 or later
Microsoft Windows 2000 Professional with Service Pack 4 or later
FactoryTalk Administration Console
Minimum: Intel Pentium III, 600MHz, 512MB RAM

Recommended: Intel Pentium 4, 2GHz or higher, 1GB RAM or more
Operating Systems:
Rev. 121908
Page 8
FactoryTalk Historian Site Edition Network Client
Minimum: Intel Pentium III, 600Mhz, 512MB RAM

Recommended: Intel Celeron, 3GHz or higher, 1GB RAM or more
Operating Systems:
Note: FactoryTalk Administration Console is tested on operating systems installed from original
Microsoft media only. Some Microsoft operating system service packs and hot fixes are not
compatible with FactoryTalk Historian Site Edition. To find out if there are any problems with a
particular Microsoft update, click the "FactoryTalk Historian SE Operating System and Service
Pack Compatibility" link in the Rockwell Automation Knowledgebase
Choosing a Setup Type

Historian Server Installation
This choice installs the Historian server, the System Management Tools, the Interface
Configuration Utility, and the LiveData interface. This will install the FactoryTalk Historian
system and its components and the FactoryTalk LiveData interface in one box so that the system
can be started with minimal configuration.
Historian Interface Installation
This choice installs the System Management Tools, the Interface Configuration Utility, the
LiveData interface, and the buffer management service. Select this option if you are installing
the interface tools on a machine other than the machine hosting the server.
Selected Components and Tools
This option allows you to choose which components you want to install. If you choose this
option, the Custom Setup screen displays when you click [Next].
Rev. 121908
Page 9
Architecture Examples
Rev. 121908
Page 10
The Virtual Machines

In this class there are three virtual machine images being used. The first is called VM-DATA1. This image is the data server for the class. It is already loaded with the following software
products:
FactoryTalk Services Platform
FactoryTalk Network Directory
FactoryTalk Activation Server
FactoryTalk View SE
FactoryTalk Historian Interface
The second virtual machine image is called VM-CLX. This image will serve as the CLX
Controller(s) that we will be collecting data from. It is already loaded with the following
software products:
RSLogix 5000
SoftLogix 5800
RSLinx Classic
RSLinx Enterprise
Rev. 121908
Page 11
FactoryTalk Activation Client
The third virtual machine image is called VM-HIST-1. This image will be loaded with the
FactoryTalk Historian server software. It is already loaded with the following software products:
Microsoft Excel
Rev. 121908
Page 12
Exercise:
Part A - Install the FactoryTalk Historian Server Component
At this point we are ready to install the FactoryTalk Historian server component on the VMHIST-1 image. This image is pointing to the FactoryTalk Network Directory located on VMDATA-1.
Note: This portion of the installation may have already been done on your computer.
Verify with your instructor if you should complete these steps or skip to the next section.
1. Verify that you are on the VM-HIST-1 image by checking for the following in the upper-left
corner:
2. Log in to the VM-HIST-1 image. Use the following credentials:

o User name:
Administrator
o Password:
rockwell
3. Run the setup.exe located in the FactoryTalk Historian SE installation folder. (Instructor
will provide specific path to supplemental class files)
4. Select the Install FactoryTalk Historian Site Edition option:
Rev. 121908
Page 13
5. Click Next
6. Select the I accept the terms in the license agreement
Rev. 121908
Page 14
7. Proceed through the wizard until you get to the point where you are asked for your product
serial number. User the serial number: 1234567890
8. Proceed through the wizard and select the Historian Server Installation type:
Rev. 121908
Page 15
9. Verify that you have selected the Server installation by checking that the FactoryTalk
Historian Server component is listed in the New or Upgraded Components list and
then click Install: This will install all of the components.
10. If the following dialog box appears, select Next to start installing MSXML Parser (note
that if MSXML Parser is already installed by other software on the computer the following
several installation procedures will be skipped):
Rev. 121908
Page 16
11. Select that you accept the terms and click Next.
12. Click Next:
Rev. 121908
Page 17
13. Click Install to proceed:
14. Click Finish:
Rev. 121908
Page 18
15. When prompted, make the following FactoryTalk Activation installation selections:
a. DEselect Install FactoryTalk Activation
b. DEselect Specify FactoryTalk Directory Server location
c. Click Finish
16. When you are prompted to reboot, click Yes
Rev. 121908
Page 19
Verify FactoryTalk Historian Administration Privileges

In this class we will be using the local machine Administrator account to administrate the
FactoryTalk Historian system. The Administrator account must have the appropriate privileges
in the FactoryTalk Historian system. This should have occurred automatically in the
FactoryTalk Historian install process, but we want to verify the Windows Administrators
user group is a member of the new FTHAdministrators group.
1. Verify that you are on the VM-DATA-1 image by checking for the following in the upperleft corner:
2. In the FactoryTalk Administration Console, open the FTHAdministrators group by

double-clicking on its entry under the User Groups folder:
Rev. 121908
Page 20
3. Verify Windows Administrators are members of the FTHAdministrators group as

follows:
3a. If not, you could click on the Add button (dont do this if they are already
there):
Rev. 121908
Page 21
3b. Click on the Windows Administrators group, and click the OK button:
3c. Then click the OK button:
4. Close the FactoryTalk Administration Console.
Rev. 121908
Page 22
Verify FTH Server is running using AboutPI-SDK

1. Verify that you are on the VM-HIST-1 image by checking the hostname on the background
image:
2. On the VM-HIST-1 image, we want to adjust the default connection timeout setting. Launch
the AboutPI-SDK utility:
3. Click on the Connections entry:
Rev. 121908
Page 23
4. Change the Connection Timeout to 30 seconds and click the Save button. Note we
are using 30 seconds for training purposes. In your actual applications you may set this value
lower or higher:
5. Check the VM-HIST-1 check box and verify the connection and click Close
Rev. 121908
Page 24
Verify Current and Archived Data using the System Management Tools
1. Do the following steps
From the Start Menu select Programs>Rockwell Software>FactoryTalk
Historian>System Management Tools

a. Check the VM-HIST-1 check box
b. Expand the Data folder and select Current Values
c. Select the Tag Search Icon
Rev. 121908
Page 25

a. Click the Search button (you may have to click it twice)

a. Select the SINUSOID tag
b. click OK

a. Verify that the SINUSOID tag has a value
Rev. 121908
Page 26

a. From the Data folder select the Recorded Values
b. Click the Tag Search icon

Rev. 121908
Page 27

a. Select the SINUSOID tag
b. Click OK

a. Click the Get Events button

a. Verify that you have Archived value(s) (will be different than below)
Rev. 121908
Page 28

a. Expand the Operations folder and select Licensing
b. Select the Resources folder and select PointSourceLimit FTLD (the
FactoryTalk Live Data Interface)
c. Note that at this time there is no valid FT Activations for the FTLD interface (no
limits defined)

a. Close the System Management Tools (SMT)
Rev. 121908
Page 29
Register the FactoryTalk Historian and Local Interface

Now that the server and local interface have been installed, we need to register these components
with the FactoryTalk Directory.
corner:
2. Launch the FactoryTalk Administration Console:
3. When prompted, select the Network FactoryTalk Directory:
4. Notice that network application data servers are not fully configurable from this image since
RSLinx Enterprise has not been installed locally:
Rev. 121908
Page 30
5. Expand the System - Connections tree. Right-click on the Historical Data folder and
select the New Historian Server Connection entry.
6. Click the Test Server Connection button:
Rev. 121908
Page 31
7. Verify that the server was found and then click the Finish button. Do NOT click Next.
Note: The Next box will open the Auto Discovery wizard which we will use in a future
lesson.
8. Right-click on Production Historian and select Properties
Rev. 121908
Page 32
9. The following dialog box will show a description and Server of VM-HIST-1 listed.
10. Click the Licensing tab, enter 1 in the Assigned box for FHLD 2500 (the 2500 tag license
that is installed and has been found on the FactoryTalk Activation Server). Then, click OK.
Rev. 121908
Page 33
11. Verify that the Production Historian and FTLD1 interface now show up under the
Historical Data folder: Right mouse click on FTLD1 and select Properties
12. In the Service Status section, notice default Startup Type is Automatic. Then, click the
Start button; wait until Started appears under Service Status, and finally the OK
button.
Rev. 121908
Page 34
[Optional] Create VM-HIST-1 Desktop Shortcuts

The installation of FactoryTalk Historian created a new Start menu program group. There are
several utilities in that group which will be used throughout this course. You may wish copy one
or more these shortcuts onto your desktop to provide easier access during the course.
1. If you wish to create desktop icons, simply Ctrl-drag and drop the shortcuts from the Start
menu onto the desktop:
IMPORTANT NOTE: Always Use Stop FT Historian SE system Shortcut

From this point on, you should always use the Stop FT Historian SE system shortcut before
you shutdown, restart, reboot, or even pause the VM-HIST-1 image. This will ensure that all
subsystems are shutdown cleanly, which may not always happen if you rely on them
automatically shutting down in response to an operating system shutdown request.
Rev. 121908
Page 35
Add data points to the local interface

1. Do the following steps:
a. From the Start menu open the FactoryTalk Administrator Console

a. Select the Network option
b. Click OK
Rev. 121908
Page 36

a. Select the InstaCorp application
b. Right mouse click and select Add Individual Historian Points

a. Click Browse Tags
Rev. 121908
Page 37

a. Expand the InstaSoap, Mixing and CLX1 folders and click on the
Online folder
b. In the right pane select TI100
c. Click on the Add Tag(s) to List button
d. Click OK
Rev. 121908
Page 38

a. Click OK
b. Close the FactoryTalk Administration console

a. From the Start Menu select All Programs>Rockwell Software>FactoryTalk
Historian SE>System Management Tools
Rev. 121908
Page 39

a. Check the VM-HIST-1 check box (if not already checked)

a. Click the Search button (you may have to click it twice the first time to give
focus to the dialog box and the second time to actually click the button)
Rev. 121908
Page 40

a. Select the TI100 tag
b. Click OK

a. Verify that the TI100 tag has a value
b. Click the Start Updating button and verify value changes
Rev. 121908
Page 41

b. Click the Tag Search icon

Rev. 121908
Page 42

a. Select the TI100 tag
b. Click OK

a. Click the Get events button

a. Verify that you have Archived values
b. Close the SMT tool
Rev. 121908
Page 43
17. To ensure that the FactoryTalk Historian Server detects licenses, refreshes
configurations done to this point, etc, select Stop FactoryTalk Historian SE system
(from Start All Programs Rockwell Software FactoryTalk Historian SE).
18. Once all the services stop, select Start FactoryTalk Historian SE system (from Start
All Programs Rockwell Software FactoryTalk Historian SE) and wait for all the
services to start again before continuing.
Rev. 121908
Page 44
Part B - Install the Distributed Interface Node software

Because data buffering is only available on interfaces installed on computers other than the
historian server, we will install that FactoryTalk Live Data interface on the VM-DATA-1 image.
2. Run the setup.exe located in the FactoryTalk Historian SE installation folder. (Ask
instructor for exact location)
3. Select the Install FactoryTalk Historian Site Edition option:
Rev. 121908
Page 45
4. Click Next
Rev. 121908
Page 46
Serial Number. User the serial number: 1234567890 and click Next.
7. Proceed through the wizard and select the FactoryTalk Historian Interface Installation
type and click Next:
Rev. 121908
Page 47
8. Verify that you selected the correct setup type by verifying the two entries in the New or
Upgraded Components list and then click Install: This will install all the components.
9. On the following dialog box select Next.
Rev. 121908
Page 48
10. Continue through the wizard until the following activation dialog appears. Make the
following FactoryTalk Activation installation selections:
o DEelect Install FactoryTalk Activation
o DEselect Specify FactoryTalk Directory Server location
o Click Finish
Rev. 121908
Page 49
[Optional] Create VM-DATA-1 Desktop Shortcuts

The installation of the FactoryTalk Live Data interface created a new Start menu program
group. There are a couple utilities in that group which will be used throughout this course. You
may wish copy one or more these shortcuts onto your desktop to provide easier access during the
course.
If you wish to create desktop icons, simply Ctrl-drag and drop the shortcuts from the Start
Rev. 121908
Page 50
Register the FTLD Distributed Interface

Now that the distributed interface has been installed, we need to register these components with
the FactoryTalk Directory. We will perform this function on the historian server.
corner:
4. Right-click on the newly registered Production Historian and choose the New Data
Collection Interface option:
Rev. 121908
Page 51
5. Using the drop-down boxes, change the Computer hosting the interface to VM-DATA-1,
then click Apply.
Rev. 121908
Page 52
6. Use the Start button to start the remote data collection interface service. Click OK
when finished:
7. Verify that the FTLD2 interface is now displayed under the Production Historian:
Rev. 121908
Page 53
FactoryTalk Historian Add Data Points

FactoryTalk Historian provides wizard which can interrogate FactoryTalk directory data sources
and configure their data points for collection.
image:
4. In the network tree, right-click on the InstaSoap area and choose the Add Individual
Historian Points context-menu entry:
Rev. 121908
Page 54
5. Select the FLD2 data collection interface, then click the Browse Tags button.
Rev. 121908
Page 55

a. Expand the InstaSoap, Mixing and CLX1 folders and click on the Online
folder
b. In the right pane select T100_Sim_Vol
c. Click on the Add Tag(s) to List button
d. Click OK
Rev. 121908
Page 56
7. Select OK on the following dialog:
Rev. 121908
Page 57
Verify tags are collecting and archiving data with SMT

a. From the Start Menu select All Programs>Rockwell Software>FactoryTalk

a. Check the VM-HIST-1 check box
Rev. 121908
Page 58


a. Select the T100_Sim_Vol tag
b. Click OK
Rev. 121908
Page 59

a. Verify that the T100_Sim_Vol tag has a value
b. Click Start Updating and verify value changes

b. Click the Search icon
Rev. 121908
Page 60


a. Select the T100_Sim_Vol tag
b. Click OK
Rev. 121908
Page 61

a. Click the Get Events button

a. Verify that you have Archived values
b. Close the SMT tool
Rev. 121908
Page 62
Add Historian Server Connection on Distributed Interface Node

We can use the FactoryTalk Administration Console to perform basic scan class configuration on
the remote interface. For more advanced configuration, we must use the System Management
Tools (SMT) and Interface Configuration Utility (ICU) installed locally on the VM-DATA-1
image. In order to use these tools, we must configure a connection to the Historian Server.
2. Launch the About PI-SDK utility:
Rev. 121908
Page 63
4. Choose Add Server from the Server menu:
5. Input the Network Node of VM-HIST-1. Uncheck Confirm. Click OK:
Rev. 121908
Page 64
6. We now want to remove the useless connection to VM-DATA-1 on which there is no

historian server. DO NOT click on the checkbox, click on the name VM-DATA-1 on the
server list:
7. From the Server menu, choose Remove Selected Server:
Rev. 121908
Page 65
8. Confirm the removal of the VM-DATA-1 connection by clicking Yes:
9. Change the Connection Timeout to 30 seconds and then click the Save button. Note
that the Connection Timeout setting may be more or less in your own applications::
10. Check the box next to VM-HIST-1 and confirm you can connect. Close the Connection
Manager application and then close the About PI-SDK application.
Rev. 121908
Page 66
Enable Buffering on Distributed Interface Node

We are using a distributed interface node because buffering cannot be enabled on interface
located on the same computer as the FactoryTalk Historian server. We have not yet configured
the distributed interface node to use buffering, so up to this point we are still vulnerable to data
loss caused by network connectivity problems or a shutdown on the historian server. In this next
section, we will configure and enable buffering on VM-DATA-1.
2. Launch the System Management Tools (SMT).
3. If not already selected, click on the VM-HIST-1 checkbox in the upper-left corner of the
screen:
Rev. 121908
Page 67
4. Select the Trusts plug-in under the Security category:
5. You should notice a Trust named PIBuffSubSystemService associated with application

pibufss.exe. This is the Trust that the system uses to allow buffering.
6. Close the SMT and launch the Interface Configuration Utility:
Rev. 121908
Page 68
7. From the interface combo box Select the FTLD2 (FTLData2) VM-HIST-1
8. From the Tools menu select Buffering
9. On the Choose Buffer Type section, click the radio button for Enable buffering with PI
Buffer Subsystem and click the Yes button on the confirmation dialog:
Rev. 121908
Page 69
10. Wait until the status box shows Current Configuration: Good and then click on the
Buffered Servers configuration section:
11. In the Buffering to collective/server drop-down, select VM-HIST-1 and then click the
OK button:
Rev. 121908
Page 70
12. Read the dialog box that appears and click Yes:
13. Back in the main ICU dialog, click on the Service section:
Rev. 121908
Page 71
14. If the interface starts before the buffering subsystem has started, data will be lost. To prevent
this, all interfaces on the buffered node should be made dependant on the buffer subsystem
service. Click Yes when the ICU offers to configure this for you:
15. Restart the FTLD2 interface by clicking the Restart interface service toolbar button:
Rev. 121908
Page 72
16. When the status bar returns to Ready and Running close the ICU as configuration is
complete:
Rev. 121908
Page 73
Part C - Installing Visualization Applications

1. Install FactoryTalk DataLink on VM-HIST-1
FactoryTalk DataLink is a Microsoft Excel add-in that allows both historian configuration and
reporting. Microsoft Excel is already loaded on VM-HIST-1 so we only have to install
FactoryTalk DataLink and register the add-ins with Excel.
1. Verify that you are on the VM-HIST-1 image by checking for the following in the upperright corner:
3. Select the Install Other Components option:
Rev. 121908
Page 74
4. Select the Install FactoryTalk Historian DataLink option:
5. Proceed through the wizard, choosing a Typical installation when appropriate:
Rev. 121908
Page 75
6. When the wizard is completed, launch Excel 2003:
7. From the menu, choose Tools - Add-Ins:
Rev. 121908
Page 76
8. Click on the Browse button:
9. Browse to the file:

o C:\Program Files\Rockwell Software\FactoryTalk
Historian\Server\PIPC\SMT\PITagCnf.xla
Rev. 121908
Page 77
10. Click on the Browse button again and find the following file:
Historian\Server\PIPC\MDBBuilder\MDBBuilder.xla
11. Click on the Browse button a third time and find the following file:
Historian\Server\PIPC\Excel\pipc32.xll
Rev. 121908
Page 78
12. Click OK on the Add-Ins dialog box:
13. Click OK on any ActiveX warnings:
Rev. 121908
Page 79
14. The PI, PI-SMT, and PI-SMT - Module Database Builder menus should now be
available:
Note: The pipc32.xll file that you added is the one that results in the PI menu. The PI menu
items are the DataLink functions. The PITagCnf.xla file is the PI Tag Configurator and the
MDBBuilder.xla file is the Module Database Builder. These two Excel Add-Ins are not part
of the DataLink install, but were installed automatically by the FactoryTalk Historian Server
install.
15. Close Microsoft Excel.
Rev. 121908
Page 80
2. Install FactoryTalk ProcessBook on VM-HIST-1

corner:
2. Run the setup.exe located in the FactoryTalk Historian SE_PB installation folder. (Ask
3. Select the Install FactoryTalk Historian ProcessBook option:
Rev. 121908
Page 81
4. Proceed through the wizard and select a Typical setup type:
5. When the wizard finishes, reboot the image when prompted:
Rev. 121908
Page 82
[Optional] Create ProcessBook Desktop Shortcut on VM-HIST-1

Throughout the rest of this course we will often use the ProcessBook application. You may wish
to create a desktop icon shortcut for launching ProcessBook more easily.
1. If you wish to create the desktop icon, simply Ctrl-drag and drop the ProcessBook shortcut
from the Start menu onto the desktop:
Rev. 121908
Page 83
3. Install FactoryTalk View SE Updates on VM-DATA-1

Rev. 121908
Page 84
4. Select the Install FactoryTalk View Site Edition Updates option:
5. Continue through the installation wizard and choose the Typical setup when prompted:
Rev. 121908
Page 85
6. Continue through the wizard to completion:
Rev. 121908
Page 86
4. Install FactoryTalk Historian ActiveView on VM-HIST-1

corner:
2. Run the setup.exe located in the FactoryTalk Historian SE_AV installation folder. (Ask
3. Select the Install FactoryTalk Historian ActiveView option:
Rev. 121908
Page 87
4. Proceed through the installation wizard and select a Typical setup when prompted:
5. When prompted, reboot:
Rev. 121908
Page 88
6. When the system finishes rebooting, log back in and launch the Internet Information
Services (IIS) Manager application:
Rev. 121908
Page 89
7. Right click on the VM-HIST-1 (local computer) entry and select the Properties
context-menu item:
8. Click on the MIME Types button (MIME is an acronym for Multipurpose Internet Mail
Extensions):
Rev. 121908
Page 90
9. Click on the New button:
10. Fill in the following and then click the OK button:

o Extension:
.pdi
o MIME type:
application/octet-stream
Rev. 121908
Page 91
11. Click the OK button:
13. Close all applications. You have finished installing all programs and completed this
exercise.
Rev. 121908
Page 92
This page intentionally left blank
Rev. 121908
Lesson 2
Discover Historian Points (Version 2.1)
What You Will Learn
How to use the FactoryTalk Historian auto-discovery wizard

to locate and configure data points for collection.
In a ControlLogix processor that is running in the VM-CLX image, there are six tag structures
using a User-Defined Data type. These structures are as follows:
Each of these structures consists of several members. PV (process variable) is one of them:
FactoryTalk Historian provides an auto-discovery wizard which can interrogate FactoryTalk

directory data sources and automatically configure their data points for collection. In this
exercise we will use the wizards advanced rules definition to specifically select the PV values
from this group of tags for collection by the historian server.
Rev. 121908
Lesson 2 Discover Historian Points (Version 2.1)
Page 2
Exercise:
corner:
4. In the network tree, right-click on the InstaSoap area under the InstaCorp application
and choose the Discover Historian Points context-menu entry:
Rev. 121908
Page 3
5. Begin by DEselecting the Linx Classic, Other OPC_DA Servers and HMI/Alarm
Servers checkboxes. Then, click the Edit Discovery Rules button:
6. On the following dialog box, you can use options to create or select Rules for the discovery
wizard to use. You could also create or select defined Tag Attributes. Click the Rule
File Management button.
Rev. 121908
Page 4
7. The following dialog has no rules defined. Click the New button:
8. On the following dialog, enter the Rule File Name and Description specified, then click
OK:
Rev. 121908
Page 5
9. Check the Active checkbox, and then click Open:
10. You should return to the following dialog. The rule file you created should be listed as
Current Rule File. Click New to define the discovery rules that will be used:
Rev. 121908
Page 6
11. The Define Discovery Rule dialog will let you define what we are going to be searching
for. Define that we are looking or ControlLogix tags that have PV as a member and the
specific part of the tag is the .PV value by making the selections highlighted below. DO
NOT CLICK OK YET!:
12. Now, in the Using this configuration: selection box, select <New Configuration>:
Rev. 121908
Page 7
13. This dialog will let us define some Tag Attributes that will be used as the tags are brought
into Historian. Enter the File Name and Eng Units selections as follows:
14. Click on the Archive tab, and change Span to 150. Then, click OK:
Rev. 121908
Page 8
15. The dialog should appear as follows. Click OK:
16. The Rule Editor dialog should now appear as follows. Click Save. Then, a Close button
will appear. Click Close:
Rev. 121908
Page 9
17. You will return to the Discover New Historian Points dialog box where you can select
Next to conduct the search:
18. You will see this window while the discovery process is performed. Discovery can take
several minutes. You should not be alarmed if several minutes go by without any points
being added. We used a relatively narrow specification for discovery in this exercise:
Rev. 121908
Page 10
19. When the discovery process is completed, you will be presented with a list of the matching
points. You have the opportunity to deselect individual or groups of points, change the scan
class for individual or groups of points, or even open a tag browser interface to add more
points. Click the Confirm Points button:
20. The completion dialog confirms that 6 data points were added to the historian using interface
FTLD1. Remember that it may take up to two minutes for the interface is be notified and
begin collection of the new points. Click the OK button and then close the FactoryTalk
Administration Console:
Rev. 121908
Page 11
At this point in the exercise, you have use the auto-discovery wizard to bring 6 tags into your
Historian database. While using the wizard, the choices you made caused the following:
The six tags are from a ControlLogix controller and are from tags with members of
PV and the actual tags are those that end with .PV.
The tags are in the Historian database with the following attributes, modified from
the defaults:
o Engineering Units of seconds
o Span of 150
The remainder of this lab will have you create a Trend in ProcessBook to test one of the
tags you created. You could also use System Management Tools (SMT) to view current or
recorded values for the tags.
1. Launch ProcessBook:
2. Select the VM-HIST-1 Server by clicking OK.

3. Click on the New toolbar button:
4. Select new ProcessBood Display (.pdi) File, set the Display Name to Test, and click
the OK button:
Rev. 121908
Page 12
5. Change to build mode by selecting the Build button on the toolbar:
6. Select the Trend button on the toolbar:
7. Drag a box in some empty space to create a trend:
Rev. 121908
Page 13
8. Click on the Tag Search button to select the following tag (refer to previous lessons for
detailed steps):
InstaCorp.InstaSoap.Soap Mixing.RSLinx Enterprise:CLX1.T100_Demo_Temp.PV
Set the Plot Time Start to *-10 Minutes. Click the OK button:
Rev. 121908
Page 14
9. Verify that the tag is recording data:
10. Close the ProcessBook application. This exercise is finished.
Rev. 121908
Lesson 3
Understanding Tags and Using
Excel Tag Configurator
What You Will Learn
Concepts, terminology and definitions of tags and

their attributes.
How to use the Tag Configurator in Microsoft Excel to
perform bulk tag creation and manipulation.
Understanding Tags
Points, sometimes also called tags, are the basic building blocks of a Historian system, because
they are how you track the events that comprise your data history. When the System Manager or
Field Services engineer installs a Historian Server, he creates a Historian Point for every source
of data that the Historian System needs to track.
Each point has more than 50 attributes that define exactly how the data should be collected for
that point. These attributes determine how frequently the point gets new values, the data type of
the point values (whether integer or string, for example), who is allowed to view and/or edit the
point, and so on. The Historian Base Subsystem stores points and their attributes in the Point
Database.
The System Management Tools (SMT) contains many tools used to manage the Historian
System:
Rev. 121908
Lesson 3 Understanding Tags and Using Excel Tag Configurator
Page 2
During the installation exercise, we used the SMT tools of DataCurrent Values and DataRecorded Values to verify that Historian was connected to the CLX controller and able to
read and record tag values.
The SMT also has a very important tool for creating, monitoring and/or editing the configuration
of tags. This tool is PointsPoint Builder.
When PointsPoint Builder is selected, such as in above graphic, the right portion will allow
you to create new tags, or edit existing tags after using the search feature. A number of tabs that
appear for the editing of the tags are:
General
Archive
Classic
Security
System
Rev. 121908
Page 3
The tabs that are most often used to monitor and/or edit Tags that come from our FactoryTalk
Live Data (FTLD) Interfaces are as follows. Note: Not all tabs and fields are listed below.
See online help and/or other FactoryTalk Historian SE reference manuals for additional
details.
General Tab:
Name:
The Tag attribute specifies the name of the point/tag. Many Historian users use the terms tag and
point interchangeably, which is fine. Technically though, the tag is actually just the name of the
point. Follow these rules for naming Historian points:
The name must be unique on the Historian Server
The first character must be alphanumeric, the underscore (_), or the percent sign (%)
No control characters are allowed; such as linefeeds or tabs
The following characters are not allowed: * ? ; { } [ ] | \ `
Point Source:
Identifies the source interface for this tag. Tags coming from FactoryTalk Live Data will be
identified with FTLD.
Engineering Units (Eng Units)
The Engineering Units field is optional.
Extended Descriptor (Exdesc)
The Extended Descriptor field is not used for most FTLD tags. However, for an Event
Triggered Input tag, this field will store the event that triggers the read of this type of tag.
Source Tag
For a standard FTLD input tag, the Source Tag field is not used. If a tag is configured as an
Output Tag, the Source Tag field identifies the tag that will be used as the source of the data to
be output (written) and also acts as a trigger tag (the source tag changing triggers a write to
the destination tag).
Rev. 121908
Page 4
Archive Tab:
Zero, Span and Typical Value

The Zero, Span, and Typical Value attributes specify the range of values for a point.
Zero Indicates a points lowest possible value. Zero does not have to be the same as the
instrument zero, but that is usually a logical choice. This attribute is required for all
numeric data type points and is critically important for float16 points.
Span The difference between the top of the range and the bottom of the range. This
attribute is required for all numeric data type points.
Typical Value Documents an example of a reasonable value for this point. For a numeric
tag, it must be greater than or equal to the zero, and less than or equal to the zero plus the
span.
Scan
Interfaces that honor this attribute will not update points whose scan flag is set to OFF.
Archiving
The archiving flag must be set to ON (1) for a point to be archived. This flag can be set to OFF
(0) to stop archiving of a point.
Step
The step flag affects only numeric points. It defines how numeric archived values are
interpolated. The default behavior, step OFF (0), treats archived values as a continuous signal.
Adjacent archived values are linearly interpolated. For example, at 12:00:00, the value 101.0 is
archived and at 12:01:00, the value 102.0 is archived. A request for the archive value at 12:00:30
would return 101.5.
A step flag of ON (1) treats the archived values discretely. Adjacent archived values are not
interpolated; an archived value is assumed constant until the next archived value.
Shutdown
In some cases it is useful to record when the Archive was shut down. That way there is a clear
indication of a gap in the data collection. Points may be configured so that Historian will
Rev. 121908
Page 5
automatically add a shutdown event with the timestamp of the Historian Server shutdown. These
events are called shutdown events.
The shutdown flag for a point is set to TRUE (1) to indicate that shutdown events should be
recorded for this tag. The default is TRUE.
For points collected from interfaces on distributed collection nodes, set this flag to FALSE (0)
because data buffering will retain the data until the home node is running again. Therefore, there
are no data gaps to identify with shutdown events.
Compressing
The compression flag should be set to ON (1) for most points. With compression off, every value
sent to the Snapshot is saved in the archive.
Compression should be turned on for all real-time points in the system. Compression affects
digital points, since a new value is recorded only when the current value changes.
Exception Deviation and Compression Deviation
Exception reporting specifications determine which events the interface sends to Historian and
which it discards. These options/features will be discussed in much more detail in a future
lesson.
Classic Tab:
Location 1-5:
The uses of Location fields are based on the type of Point Source of a tag. In the case of
FTLD Point Sources, the Locations are used as follows:
Location1: Defines the Interface ID (FTLDx, where x is the ID). The DEFAULT is 1,
typically used when the Interface is installed on the FTHSE Server. If Interfaces are
installed remotely (on non-FTHSE computer, typically on a remote FTView SE and/or
Rev. 121908
Page 6
RSLinx Enterprise computer), then you would reference that Interface ID (typically 2 or
larger).
Location2: Not used
Location3: Tag type
o 0: Polled or Event Trigger Input point
o 1: Unsolicited/Advised Input point (DEFAULT is 1)
o 2: Output point
Location4: Scan class number (DEFAULT is 1, equates to 1 second scan rate). The scan
class number is defined in the Data Collection Interface Properties. This is found in the
FactoryTalk Administration Console (FTAC)>System>Connections>Historical
Data>Production Historian>FTLD1>Scan Classes tab which appears as follows:
Location5:
o Version 2.0 - Not used
o Version 2.1 Polled from cache 0 (default), Polled from device 1 (only use
for event triggered tags)
Instrument Tag:
For a standard Polled or Advised Mode FTLD tag, the Instrument Tag field is identifying the
actual location from where the data from this tag is coming from. If using Discover Historian
Rev. 121908
Page 7
Points or Add Individual Historian Points wizards, the contents of the Instrument Tag
field will automatically match the name of the tag. However, names of tags can be modified,
which often would be desirable. If the name of a tag is modified, the Instrument Tag field
would still point to the actual source of data, the original tag in the CLX processor, for
example.
For a tag configured as Output Mode, the Instrument Tag field identifies where the data from
the Source Tag is being written to (the destination of the data transfer).
If Tags are no longer needed:

Decommissioning Points
Typically, to decommission a point, you set the Scan attribute to 0 (off):
1. Open SMT and select the PI Server for that point.
2. In the System Management plug-ins list, under Points, choose Point Builder.
3. Search for the point.
4. Click the Archive tab.
5. Under Scan, click Off.
Deleting Points
When you delete a point, you lose all data for that point, so you break any client displays that use
the point. Further, once you delete a point, you can't get it back. If you are unsure about the
purpose of a points existence or about the need for any historical data associated with it, its
safer to decommission the point rather than deleting it.
Rev. 121908
Page 8
Tag Configurator
FactoryTalk Historian comes with a useful add-in for Microsoft Excel called the Tag
Configurator. This add-in shows up as the PI-SMT menu in Excel. Using this add-in we can
perform bulk tag management tasks such as creation, modification, and even deletion. In this
exercise we will be using the Tag Configurator to automatically create historian tags as well as
to do bulk modifications of tags.
image:
2. Launch Excel 2003:
3. Click the Open toolbar button and open the file Ex08 BA2 Tags.xls located in the
class files folder (ask instructor for exact location):
4. Note the information in the spreadsheet. The text at the top of the columns indicates what
information is contained in the cells below. Items such as the name of the Tag, if archiving is
on or off, when this tag was last changed and by who, settings for Compression (deviation,
percent and max), etc, are contained within this spreadsheet.
Rev. 121908
Page 9
5. Verify that the Tag Configurator was installed properly in Exercise 1 by checking for
the existence of the PI-SMT menu in Excel. If this menu does not appear, recheck the
DataLink installation section of Exercise 1.
6. We want to add these tags to the FactoryTalk Historian system for use in a later exercise,
so choose the Export Tags entry on the PI-SMT menu:
Rev. 121908
Page 10
7. On the Export PI Tags dialog, verify that the Mode is set to Create and then
click the OK button:
8. Acknowledge the results dialog by clicking the OK button:
9. Our new tags will start being collected within a couple of minutes. Create a new
workbook to work with by clicking the New toolbar button:
Rev. 121908
Page 11
10. We are going to import into Excel the tags that we discovered in a previous exercise.
Select the Import Tags command on the PI-SMT menu:
11. Set the Tag Mask to *.PV and verify the Point Source is ftld then click the
OK button:
Rev. 121908
Page 12
13. We want to collect six .SCA member tags so we will use the .PV tags as a template.
Begin by dragging a selection box around the six Tag names in column B:
Rev. 121908
Page 13
14. Select EditFind and configure the dialog as follows and select Replace All::
15. You should now have all tags listed with .SCA at the end instead of .PV
16. Note that column AA is identified as instrument tag and contains the same .PV tags
that column B had:
Rev. 121908
Page 14
17. Use the same find and replace procedure to also change all of these tags to .SCA
instead of .PV:
18. To create the new tags, select the Export Tags command on the PI-SMT menu:
Rev. 121908
Page 15
21. Our new tags will start being collected within a couple of minutes. At this point we
would like to modify the compression parameters for all of our temperature data points.
We will use the Tag Configurator to make these changes en masse.
First we need to clear out the worksheet from our previous efforts. On the PI-SMT menu,
choose the Clear Sheet command:
22. Click Yes to confirm clearing the current sheet:
Rev. 121908
Page 16
23. Select the Import Tags command on the PI-SMT menu:
24. This time, set the Tag Mask to *Temp.* and verify the Point Source is set to
ftld then click the OK button:
Rev. 121908
Page 17
25. We want to ensure that any compressed interpolated temperature value is within 0.6 of
what the uncompressed interpolated value would have been. We also want to have an
archived value at least every minute. To satisfy the first condition, we specify a
CompDev of 0.6.
Use your copy and paste skills to change the compdev column (F), to 0.6 for all tags:
26. Important to realize that CompDevPercent will ALWAYS override CompDev. So, for
the CompDev values to be used, we must now delete the compdevpercent column,
G, from the worksheet. Select the entire G column, by clicking on the letter G.
Then choose the Delete command on the Edit menu:
27. To satisfy the second condition, an archived value at least every minute, now set the
compmax column, which is now column G, to 60 (entered in seconds):
Rev. 121908
Page 18
28. Now, choose the Export command on the PI-SMT menu:
29. Change the Mode to Edit and then click the OK button:
30. Click the OK button on the results dialog:
Rev. 121908
Page 19
31. The changes to the tags will tag effect within a couple of minutes. Use the SMT tools to
verify information about the tags youve just edited such as:
Use Data-Current Values to view Current Values
Use Data-Recorded Values to view Recorded (Archived) Values
Use Points-Point Builder to verify your changes of Compression
Deviation of 0.6 Engineering Units and Max Time of 1 minute (60
seconds).
Rev. 121908
Page 20
Changing Tag Names (not an actual exercisefor informational purposes)

Note that many tag names resulting from using the Discover Historian Points and Add
Individual Historian Points can be very long, including Application, Area and Server
names such as the ones youve just been working with in this exercise:
If you dont want to work with these long, somewhat complex names, one option available
to you is in the SMT Point Builder. By selecting the Rename button, you can rename the
tag. All of the data previously archived will still be associated with this tag: For example, in
the dialog box below, after clicking the Rename button, the new name of T100_Temp
is being given to the tag originally named InstaCorp.InstaSoap.Mixing:RSLinx
Enterprise:CLX1. T100_Demo_Temp.PV:
Rev. 121908
Page 21
If wanting to change many names at once, the Tag Configurator in Excel could be very
useful. However, if one attempts to change the names in the tag field and export the tags
to Historian as an Edit, there would be errors because the exporting function would be
looking for tags with these exact names to already exist:
Bulk-changing of tag names in Excel can but done, but what must occur is a column inserted
identified as NewTag.
o Names entered into that column will be the new names for the tags, and data
previously archived will still be associated with those tags.
o If a row in that column is left empty, that tag name will not be affected.
Rev. 121908
Page 22
In the following example, notice the NewTag column that has been added and three of the
tags have new, reduced-length tag names specified. When exported, all six of the tags
were edited. But, only three of them received new names in the process
The Instrument Tag column, identified as column AA in the below, would remain with
the original, full tag names. The Instrument Tag setting for a tag identifies the actual
address and/or location of the data:
Note: If you have had time and actually followed this procedure to change your
Demo_Temp tag names, please change them back as the original names will be used
in future exercises. Sorry for any inconvenience, but thanks much for your great
initiative!
Rev. 121908
Lesson 4
Using Data Collection Modes of Polled versus Advised
What You Will Learn
Compare Polled Against Advised Data Collection Modes
In this exercise, you will compare the polled versus advised data collection modes. You will
configure two separate FactoryTalk Historian points which collect data from the same location in
the SoftLogix controller, both with no exception testing, no compression and with a exception
max time of 10 seconds. The point used in the SoftLogix should be at a constant value for a
period of at least twice the ExcMax. For this exercise you will use the T200_Temp.PV tag with a
manually initiated batch followed by a 1 minute rest, then another batch. A ProcessBook display
will then be configured to mark individual data points and illustrate the difference between the
two collection modes.
Polled Mode Collection
Set location 3 = 0 for polled mode
Poll the data source at scan interval
Works correctly with ExcMax and unchanging data
Advised Mode Collection
Set location 3 = 1 for advised mode
Does not work correctly with ExcMax and constant data values
Less network intensive than polled mode at fast scan rates
Rev. 121908
Lesson 4 Using Data Collection Modes of Polled vs. Advised
Page 2
image.
2. In the following steps you will use Excel to create and configure two separate FactoryTalk
Historian points (polled and advised mode) which collect data from the same location in the
SoftLogix controller, T200_Temp.PV.
3. Launch Excel.
4. Select the Import Tags command on the PI-SMT menu and Import the
T200_Temp.PV (full tag syntax: InstaCorp.InstaSoap.Mixing:RSLinx

Enterprise:CLX1.T200_Demo_Temp.PV ), using the following parameters:
All attributes for tag mask specification
Tag Mask :
*T200*Temp.pv
Point source:
ftld
Point Class:
classic
Rev. 121908
Page 3
5. This returns the attributes for the InstaCorp.InstaSoap.Mixing:RSLinx
Enterprise:CLX1.T200_Demo_Temp.PV tag. Change/set the specific tag attributes listed

as follows:
Tag:
6. compdev:
compdevpercent
compmax:
compmin:
compressing:
excdev:
excmax:
location3:
span:
7. typicalvalue:
T200_Demo_Temp_Polled
0
0
0
0
0
0
10
0 (Polled mode)
200
50
8. Copy this row of tag information and paste into the row below to create a duplicate row.
7. Change the attributes in this second row as follows:
Tag:
location3:
T200_Demo_Temp_Advised
1 (Advised mode)
8. Your spreadsheet should now appear as follows:
9. To create the new tags, select the Export Tags command on the PI-SMT menu.
Rev. 121908
Page 4
10. In the Export PI Tags dialog, verify that the Mode is set to Create and click the OK
button.
11. Click the OK button to acknowledge the results.
Rev. 121908
Page 5
In the following steps you will build a basic ProcessBook display with a trend for the two
new T200 points.
1. Launch ProcessBook.
2. Click the new button on the toolbar.
3. Select the type as ProcessBook Display (.pdi) File and give it the name Polled vs Advised
Trend and click OK.
4. Verify that you are in build mode by checking the build mode icon on the toolbar. It will be
highlighted (if not, click the build mode icon to change to build mode).
5. Select the Trend button on the ProcessBook toolbar.
Rev. 121908
Page 6
6. Drag a trend box into the empty space on the display.
7. The Define Trend view will appear, select the Tag Search button.
8. Select the Tag Mask to T200* and click Search.
Rev. 121908
Page 7
9. Select the two tags T200_Demo_Temp_Polled and T200_Demo_Temp_Advised, to

move them to the trend plot.and select OK.
10. Set the Max and Min scaling to Database.

11. Change the Plot Start Time to *-5m.
Rev. 121908
Page 8
12. Click the Display Format tab and check Markers checkbox.
13. Click OK.
Rev. 121908
Page 9
14. Select the Run button on the ProcessBook toolbar.
15. Save the display by clicking on the Save icon on the ProcessBook toolbar, enter Polled vs.
Advised Trend into the Name field.
16. Switch to the VM-DATA-1 image.
17. Launch FT View Studio.
18. When prompted, select the Site Edition (Network) application type and click Continue.
Rev. 121908
Page 10
19. Select the InstaCorp application and click Open.
20. Expand the View studio project path InstaSoap \ Mixing \ Mixing HMI \ Graphics \
Displays and open the process overview T200.
Rev. 121908
Page 11
21. Run the display by clicking on the Test Display icon on the FT View Studio toolbar.
22. From the Process Overview T200 display, click the Start button for the T200 Temp Cycle
(you may need to hold the button down for a few seconds watch for the words T200 Temp
Cycle Running to appear). The cycle will take approximately 50 seconds to complete).
23. Once the temp cycle has completed, leave a rest period of 1 minute and then start the temp
cycle again.
24. Return to the VM-HIST-1 image and the ProcessBook display Polled vs. Advised Trend.
25. The trend should be similar to the one shown below. The trend shows each time cycle and the
rest period between each cycle. Observe the difference between the polled and advised data
collection modes specifically at the start of each cycle.
Rev. 121908
Page 12
26. Click on the left-hand side of the trend and pull out the Trend Cursor to examine it in more
detail.
27. Return to the VM-DATA-1 image and the process overview T200.
28. Start the time cycle until the temperature reaches 149 (approx 5 sec), then stop the cycle;
wait for a period with the value constant for a period of at least twice the ExcMax (> 20 sec).
Then restart the cycle.
29. Save your work and discuss the results with the rest of the class and instructor.
Rev. 121908
Lesson 5
Buffering Distributed FTLD
Interface Data
What You Will Learn
Adding data point using the PI-SMT Excel tool

Verify buffering on a distributed FTLD interface
Plot the results in ProcessBook
Buffering
FactoryTalk Historian provides a buffering service that can save your data if the Interface Node
loses its connection to the Historian Server. When an Interface Node is running the buffering
service (bufserv), data flows from the data source, through the interface to the buffering service
and from there to the Snapshot subsystem on the Historian Server.
Data Flow with Buffering

If the Historian Server is not available for some reason (such as an upgrade on the Server) then
bufserv stores the data in a file buffer on the Interface Node. When the Historian Server becomes
available again, bufserv sends all the stored data from the buffer, in chronological order, back to
the Historian Server. At this point, if you look at the data in ProcessBook, you see a continuous
flow of data, with no gaps.
As System Manager, you should make sure that the buffering service is running on each
Interface Node. The main exception to this rule is for PINet Nodes, which perform their own
buffering. Also, a few interfaces, such as batch file and event file, work better without the
buffering service. If you're not sure whether a particular interface is compatible with the
buffering service, check the documentation for that interface.
Rev. 121908
Lesson 5 - Buffering Distributed FTLD Interface Data
Page 2
You need only one buffering service running on each Interface Node to buffer all the interfaces
for a particular Server, however you can only buffer data to one Server at a time from each
Interface Node. You can set the maximum size of the file buffer (up to 2GB) in the ICU
("Configuring Interfaces").
Impact on the Historian Server
On the Historian Server side, all data from the Buffer Subsystem comes directly to the Snapshot
Subsystem, without going through the Historian API translator of the Network Manager (in the
case of BufServ). Depending on data rate and hardware, this can potentially result in a
significantly reduced CPU load for the Historian Network Manager. Also, the Buffer Subsystem
runs the compression algorithm before all time-series data is sent to the Historian Servers. This
guarantees identical data in the archive records of all Historian Servers, but also brings another
reduction of CPU usage for the Snapshot Subsystem. Overall, the more distributed CPU load
translates into a higher scalability of your Historian System.
Note: While the Buffer Subsystem performs the swinging-door compression on the remote node,
all data from the Historian Interface or API application is sent to the Historian Server. Values are
marked as snapshot or archive values before they are stored in buffer queues and sent to the
Historian Servers. As a result, real-time updates are delivered to Client Applications, Analyses,
or Calculations as if compression was performed by the Historian Server itself.
Buffer Files
PIbufss and Bufserv cannot run at the same time. However, if PIbufss replaces BufServ, it does
not replace the buffering that the API library performs. As a result, the files APIBUF*.DAT in
the PIHOME\DAT directory still exist when using the Buffer Subsystem. However, under
normal operation these files contain no data (standard size is 16 bytes).
Instead, the Buffer Subsystem creates fixed-size event queues named PIBUFQ_*.DAT to store
all time-series data. The asterisk (*) in the file name is substituted by the host name of the
corresponding Historian Server. By default, these queue files are found in the PIHOME\DAT
directory, but their location is configurable (see Parameters and PICLIENT.INI). Default size for
these queue files is 32 MB, configurable from a minimum of 8 MB to a maximum of 128 GB. In
most cases, choose a large enough size for the PIbufss queue as it guarantees a reserved space for
buffered events. Use Performance Counters or the pibufss -qs option (see Queue File Sizing) to
estimate the correct size based on data rate and desired capacity.
Unlike the API buffer files, the PIbufss queues are circular buffers accessed through memory
mapping. This means all data in the memory buffers of PIbufss are continuously mirrored to disk
for higher reliability and scalability. If a file on disk gets entirely full, another one of the same
size is created in the same directory and a sequence number is appended to the file name. If more
data needs to be buffered, new files are created for as long as there is available disk space. See
Buffer and Cache Files for details and examples.
Rev. 121908
Page 3
Comparison Table
The following table summarizes the key differences between BufServ and PIbufss..
Element
Supported Platforms and
Operating Systems
Supported PI Node Types

Supported Historian Servers
Buffering to multiple nonreplicated Historian Servers
Manual Configuration for
HA
BufServ
UNIX (IBM AIX, HP-UX,
Compaq Tru64, Sun
Solaris), Linux (x86),
Windows NT4, Windows
2000, Windows XP, and
Windows Server 2003 (x86
and x64 versions)
All PI Nodes
PIbufss PR1
Windows 2000, Windows
XP, and Windows Server
2003 (x86 and x64
versions)
All Historian Servers

including PI2 on OpenVMS
Supported (up to 64)
Historian Server version

3.4.375 or later
Not supported
Required
(by editing PICLIENT.INI

file or by using PI ICU, PI
SMT)
(Archive data within point
compression specs)
Automatic buffer creation
N-Way Buffering
Supported
Changes to PI Collective
Configuration (such as new
replication node)
Maximum Buffering
Capacity (per Server)
Not detected
Location of Buffer Files
Buffer Files Recovery

Tools
Default Maximum
Throughput
Windows Performance
Counters
Monitoring Tools
Message Log
Interface or Client Node

(PINS required).
2 GB or available disk
Available disk space
space, whichever is less (the (buffer files can be prefile grows on demand)
sized for higher
reliability)
PIHOME\DAT directory
Configurable
(usually C:\Program
Files\PIPC\DAT)
Requires BufServ
5,000 events/second
50,000 events/second
Not available
Available under PI Buffer

Subsystem
- PIbufss interactive mode
- PIdiag utility
- bufutil (optional)
PI Message Log or
Windows Event Log
Bufutil
(PIHOME\BIN
directory)
PIPC.LOG
(PIHOME\DAT directory)
Rev. 121908
Page 4
Exercise:
Select the VM-HIST-1 image

Open Windows Explorer
From the mapped drive (or path provided by your Instructor) open the
FTH_Class_Files folder
Select the Timer1ACC Interface Tags.xls file and double-click to open the file
Rev. 121908
Page 5
3. The two tags in this spreadsheet are almost identical. The source of both tags is the same
tag in the ControlLogix processor (defined by column AA, instrument tag). The only
differences will be the tag names of these tags/points within Historian (defined by
column B, Tag) and the FTLD Interfaces the tags are coming through (defined by
column AB, location1). The Interface1 tag is coming through FTLD1 on the local
computer (VM-HIST-1) and the Interface2 tag is coming through FTLD2 on the
remote computer (VM-DATA-1) that is configured for buffering.
Select the PI-SMT tab
Select Export Tags

Verify that the Mode selected is Create
Click OK
Rev. 121908
Page 6

Verify that the export succeeded with no errors
Click OK
Close Excel

From the Start menu open FactoryTalk Historian SE ProcessBook
Rev. 121908
Page 7

Click OK

From the File menu select New

Select the ProcessBook Display option
Click OK
Rev. 121908
Page 8

Select the Trend icon
Add the Trend to the Display (drop and drag )

Click Tag Search
Rev. 121908
Page 9

In the Tag Mask textbox enter *timer1*
Click Search

Select both Timer1.ACCInterface1 and Timer1.ACCInterface2
Click OK
Rev. 121908
Page 10

Change the Plot Time Start to *-10m
Click OK
Rev. 121908
Page 11

Verify that the values for Timer1.ACCInterface1 and Timer1.ACCInterface2 are the
same and are changing
17. In order to monitor the buffering system, there are queue statistics we can monitor on
the computer with the Interface that is doing the buffering. Switch to the VM-DATA-1
image:
18. Open a Command Prompt by clicking Start Command Prompt.

19. Change to the path of:
C:\Program Files\Rockwell Software\FactoryTalk Historian\Server\PIPC\BIN
20. Your command prompt should look similar to this:
Rev. 121908
Page 12
21. Enter the command pibufss qs

(Note: pibufss is the buffer service and qs is queue statistics)
22. The result of this command should be similar to the following. The first column of
numbers is the count at that moment. The second column is change since last
update. Note that you should be accumulating Total Event Writes and Total Event
Reads, but no Current Queue Events at this time:
23. Return to the VM-HIST-1 image:
24. Right-click on My Network Places and select Properties:
Rev. 121908
Page 13
25. Right-click on Local Area Connection and select Disable:
26. Go back to the VM-DATA-1 image:
27. Since the Historian Server is disconnected from the network, you should soon see
Current Queue Events accumulating (may take several updates):
Rev. 121908
Page 14
29. In the ProcessBook display verify that the values for Timer1.ACCInterface1 and
Timer1.ACCInterface2 have stopped changing
30. Now you will open an Excel spreadsheet and modify it to display the archived values for
these two tags. At this time, no new archived values will be coming into Historian
since it is disconnected from the network. Do the following steps:
Open Windows Explorer
From the mapped drive open the FTH_Class_Files folder
Select the Timer1ACC View Interface Tags.xls file and double click to open the
file
Rev. 121908
Page 15

Select cell A3
Select Compressed Data (Start Time/Number)

Click the select tag cell icon
Rev. 121908
Page 16

Select cell A1
Click the add tag cell icon

In the Start Time textbox enter *-10m
In the Number of Values textbox enter 10000
Check the show timestamps check box
Click OK
Rev. 121908
Page 17

Select cell E3

Select PI - Compressed Data (Start Time/Number)
Rev. 121908
Page 18

Select cell E1 to add Tagname cell location
In the Start Time textbox enter *-10m
In the Number of Values textbox enter 10000
Check the show timestamps check box
Click OK
Rev. 121908
Page 19

Move down to the end of the values for Timer1ACCInterface1 and
Timer1ACCInterface2
Write down the time and value for each tag
Note: In this screen shot the time is 29 May-08 16:40:02 and the values are 34914
39. Right-click on Local Area Connection and click Enable:
Rev. 121908
Page 20
40. Go back to the VM-DATA-1 image:
41. As you monitor the queue statistics, eventually the interface will realize the server is back
on the network and will send the queued data to the server, zeroing out the Current
Queue Events (may take multiple updates, up to a minute or two):
42. Press Ctrl C to stop the queue statistics and then close the Command Prompt.
Rev. 121908
Page 21
44. Since the buffered data should now be in the Historian archive, we want to update our
spreadsheet to see the results of having buffered the data while the server was down.
Do the following steps:
Move to and select cell A3
Right mouse click and select Compressed Data (Start Time/Number)

Click OK to refresh the data
Rev. 121908
Page 22

Move to and select cell E3
Right mouse click and select Compressed Data (Start Time/Number)

Click OK
Rev. 121908
Page 23

Using the time and value from step 38 find the next value for each tag
Note: For the Timer1ACCInterface1 there is a gap in the data indicating that no
buffering occurred. For Timer1ACCInterface2 there is no gap indicating that the
Timer1ACCInterface2 data was buffered.
Rev. 121908
Page 24

On the ProcessBook Display, use the arrows on the time scale to find the time you
removed the VM-HIST-1 image from the network.
Note: For the Timer1ACCInterface1 there is a gap in the data indicating that no buffing
occurred and for Timer1ACCInterface2 there is no gap indicating that the
Timer1ACCInterface2 data was buffered.
This exercise is complete
Rev. 121908
Lesson 6
Understanding and Using Exception and Compression
What You Will Learn
Adding exception testing to a tag

Adding compression testing to a tag
Trending the differences between exception and
compression results
Exception Specifications
Most Historian interfaces use Exception Specifications to determine whether the raw values that
they receive are sent to the Snapshot Subsystem. The interface-specific documentation must be
consulted to determine whether or not the interface uses the exception specifications.
The exception specifications consist of the following attributes:
Attribute Name
ExcMin
ExcMax
ExcDev
ExcDevPercent
Point Class
Base
Base
Base
Base
Type
uint16
uint16
float32
float32
Default Value
0 seconds
600 seconds
1 eng unit
1 % of Span
Limits
0 to 65535
0 to 65535
0 to Span
0 to 100
ExcMin is the exception minimum time, ExcMax is the exception maximum time, ExcDev is the
exception deviation in engineering units, and ExcDevPercent is the exception deviation in units
of percent of span. ExcDev and ExcDevPercent are related by
ExcDev = ExcDevPercent * Span / 100
where Span is defined by the Span attribute. If either ExcDev or ExcDevPercent is changed, the
other is automatically updated to be compatible. If both are changed at once, the change to
ExcDevPercent takes precedence.
Raw values from an interface pass the exception test when the following conditions are met.
The difference between the new value and the last value that passed exception is greater
than ExcDev.
and
The difference between the timestamp of the new value and the timestamp of the last
value that passed exception is greater than ExcMin, where ExcMin has units of seconds.
or
The difference between the timestamp of the new value and timestamp of the last value
that passed exception is greater than ExcMax, where ExcMax has units of seconds.
Rev. 121908
Lesson 6 Understanding and Using Exception and Compression
Page 2
The last value that passed the exception test is called the "old value." The next value that passes
the exception test is called the "new value." In between the "old value" and the "new value" there
may be several values that are received that do not pass the exception test. The last of these
values that are received between the "old value" and "new value" is called the "previous value."
There will not be a "previous value" if the interface did not receive a value between the "old
value" and the "new value." When a new value passes exception, the "previous value" (if it
exists) and the "new value" will be sent to the Snapshot Subsystem. The "new value" will then
become the "old value," and the cycle continues. Note that the "previous value" will be sent to
Historian even if it was received before ExcMin seconds has expired. ExcMin applies only to the
"new value."
The time between exceptions can be greater than ExcMax if no new values are received by the
interface for a point.
Compression Specifications
The compression specifications determine whether events from the Snapshot Subsystem are
archived or discarded. If the compressing attribute is set to OFF, then the compression
specifications are ignored, and all events that are sent to the Snapshot Subsystem are archived in
Historian. The compression specifications are always ignored for digital Historian Points. The
compression specifications consist of the following attributes:
Attribute Name
CompMin
CompMax
CompDev
CompDevPercent
Point Class
base
base
base
base
Type
uint16
uint16
float32
float32
Default Value
0 seconds
28800 seconds
2 engunits
2 % of Span
Limits
0 to 65535
0 to 65535
0 to Span
0 to 100
CompMin is the compression minimum time, and CompMax is the compression maximum time.
CompDev is the compression deviation in engineering units and CompDevPercent is the
compression deviation in units of percent of span. CompDevPercent and CompDev are related
by
CompDev = CompDevPercent * Span / 100
where Span is defined by the Span attribute of the point. If either CompDev or CompDevPercent
is changed, Historian automatically recalculates the other attribute. If both attributes are edited
simultaneously, the change to CompDevPercent takes precedence.
Compressing Attribute
The compression attribute should be set to ON (1) for most points. When compression is OFF
(0), every value that is sent to the Snapshot Subsystem is saved in the Archive. When
compression is ON, only the values that deviate significantly from the current trend are archived.
See the description of the compression algorithm for more detail.
Rev. 121908
Page 3
Compression should be turned on for all real-time points in the system. Compression even
affects digital points, since a new value is recorded only when the current value changes or when
the compression maximum is exceeded. Sampled data, such as laboratory tested data, are typical
non-compressed points.
Attribute Name
Compressing
Point Class
Base
Type
byte
Default Value
ON (1)
Limits
OFF (0) or ON (1)
Compression
After leaving the Snapshot, events are evaluated according to the compression specifications to
see if they are significant events. If so, they are sent to the Event Queue. If not, they are
discarded. This process is called compression.
There are three instances where an event will bypass the compression process and be put in the
Event Queue:
If the Compressing attribute for the point is set to OFF.
If the timestamp is older than the timestamp of the current snapshot. Such an event is sometimes
termed "out of order."
If the Status attribute of the Point has changed.
The compression method used by Historian allows Historian to much more data online than
conventional scanned systems. The data are also much more detailed than in an archiving system
based on averages or periodic samples.
The compression method is called "swinging door compression." Swinging door compression
discards values that fall on a line connecting values that are recorded in the Archive. When a new
value is received by the Snapshot Subsystem, the previous value is recorded only if any of the
values since the last recorded value do not fall within the compression deviation blanket. The
deviation blanket is a parallelogram extending between the last recorded value and the new value
with a width equal to twice the compression deviation specification.
Each point has three attributes that comprise the compression specifications: CompDev
(compression deviation), CompMin (compression minimum time), and CompMax (compression
maximum time). CompDev is half of the width of the deviation blanket (as shown in the
illustration). CompDevPercent is similar to CompDev, but it specifies the compression deviation
in percent of span rather than in engineering units.
Just like exception reporting, compression is a filter. The difference is that the exception
specifications determine which events should be sent to Historian, whereas the compression
specifications determine which of the events sent to Historian should go into the Archive.
Rev. 121908
Page 4
CompMin and CompMax are limits that refer to the time between events in the Archive. A new
event is not recorded if the time since the last recorded event is less than the compression
minimum time for the point. A new event is always recorded if the time since the last recorded
event is greater than or equal to the compression maximum time.
The duration of time between archive events can be greater than the compression maximum
time. However, if the duration of time between events exceeds the compression maximum time
the next event will be archived even if the value is the same as the last event that was archived.
One can adjust the compression parameters to produce efficient archive storage without losing
significant data. The compression maximum time is usually set to one value for all points in the
system. It should be large enough that a point that does not change at all uses very little archive
space. A compression maximum time of one work shift (for example, 8 hours) is often a good
choice.
Zero and Span Attributes

Zero is a number that represents the lowest value that a Historian Point should ever receive. Span
is a positive number that represents the range of the data. For example, if data for a Historian
Point is expected to fall between -1000 and +1000, then the Historian point should be configured
with a Zero of -1000 and a Span of 2000.
Rev. 121908
Page 5
The care with which one should set the Zero and Span attributes depends upon a variety of
factors. For example, the Zero and Span affect the very values that are stored in the archive for
int16 and float16 Historian points. The Zero and Span are used by the Historian Data Archive,
various client applications, and some interfaces, as described below.
If the PointType attribute is int16 or float16, the Zero and Span attributes determine the
maximum and minimum values that can be stored in the Historian Archive for that point.
If a value below Zero is sent to the Historian point, the digital state Under Range is
written to the Historian point instead of the value. If a value above Zero+Span is sent to
the Historian point, then the digital state Over Range is written to the Historian point. The
actual value that is stored in the archive for int16 and float16 points is a scaled integer
between 0 and 32767. For example, if the Zero is 0 and the Span is 100 and a value of 50
is sent to the Historian point, then the value is stored as 16383. If the Zero or Span is
changed for the Historian point, then the actual value that is stored in the Archive is not
changed, but the scaled value that is displayed will be different.
For point types other than int16 and float16, the Zero and Span attributes do not affect the
values that are stored in the Archive. Values below Zero and values above Zero+Span
can be archived with no problem.
The Zero and Span Attributes should never be changed for digital Historian points. They
are set internally by the Historian Server. Changing the Zero and Span for digital points
will invalidate the point configuration.
The Zero and Span Attributes affect the displays for some client applications. In
Historian-ProcessBook for example, one can choose to scale the y-axis of trended data
according to the "database." If this option is chosen, then the Zero and Span for the
Historian point is used to scale the y-axis.
Some interfaces use the Zero and Span attributes to scale the values that are sent to
Historian. This scaling has nothing to do with the scaling of the stored archive values for
int16 and float16 Historian points that is done by the Historian Archive. One should
consult the interface-specific documentation to determine whether any scaling of
incoming or outgoing values is performed.
Attribute Name
Point Class
Type
Zero
base
float32
Default
Value
0
Span
base
float32
100
Limits
Any single-precision
floating-point number.
Any single-precision
floating-point number greater
than zero.
Rev. 121908
Page 6
Archiving Attribute
Archiving must be set to ON (1) in order for data to be archived for a Historian Point. If
archiving is set to OFF (0), all data that is sent to the Snapshot Subsystem for the point is
discarded.
Attribute Name
Archiving
Point Class
base
Type
byte
Default Value
ON (1)
Limits
OFF (0) or ON
(1)
Rev. 121908
Page 7
Add TestSignal Data Points

Select the VM-HIST-1 Image

From the Start menu open the FactoryTalk Administration Console

Click OK
Rev. 121908
Page 8

Expand the MYApp application and select Mach3
Right mouse click and select Add Individual Historian Points

Verify that FTLD1 interface is selected
Click Browse Tags
Rev. 121908
Page 9

Open the Program:MainProgram folder
Select TestSignal1, TestSignal2 and TestSignal3
Click Add Tag(s) to List
Rev. 121908
Page 10

Verify that TestSignal1, TestSignal2 and TestSignal3 are selected
Click OK
Rev. 121908
Page 11

Click OK

From the Start menu open the SMT console
Rev. 121908
Page 12

Select Points>Point Builder
Click the Search icon

In the Tag Mask textbox enter *TestSignal*
Click Search
Rev. 121908
Page 13

Select TestSignal1, TestSignal2 and TestSignal3
Click OK

select the TestSignal1 Tag
select the Archive tab
in the Span text box enter 1500
in the Exception Deviation text box enter 0
change the Exception Max time from 10 Min to 1 Hour
in the Compression Deviation text box enter 0
click the save icon
Rev. 121908
Page 14

click the save icon
Rev. 121908
Page 15

click the save icon

Select the VMWare CLX image
Rev. 121908
Page 16

From the Start Menu open RSLogix 5000

Select Communications Who Active
Select FTHistorian
Click Go Online
Rev. 121908
Page 17

Click Select File

Select FTHistorian1.ACD
Click Select
Click Upload
Rev. 121908
Page 18

Expand the MainProgram folder
Double click on MainRoutine

Select rung 6
Select TestEnable.0
Right mouse click and toggle bit on
Note: If TestEnable.0 is already on, toggle it off and then toggle it back on again
Rev. 121908
Page 19

Move to rung 9
Note: The logic will load 180 values from the TestSignal array. This will take 4-5
minutes. Wait until the PointIndex equals 180
Verify that the PointIndex has reached 180 and that the TestSignal logix has
unlatched the TestEnabled.1 bit

Select the VM-HIST-1 Image

From the Start Menu open Microsoft Office Excel 2003
Rev. 121908
Page 20

Select cell A1
From the PI menu select Compressed Data (Start Time / Number)

Click the Tagname(s) search icon
Rev. 121908
Page 21

In the TagMask enter *testsignal*
Click Search

Select TestSignal1
Click OK
Rev. 121908
Page 22

In the Start Time textbox enter *-1h
In the Number of Values enter 1000
Check the show timestamps checkbox
Click OK

Move to cell D1
From the PI menu select Compressed Data (Start Time / Number)
Rev. 121908
Page 23


Select TestSignal2
Click OK
Rev. 121908
Page 24

Click OK

Move to cell G1
Rev. 121908
Page 25

From the PI menu select compressed Data (Start Time/Number)

Rev. 121908
Page 26

Select TestSignal3
Click OK

Click OK
Rev. 121908
Page 27

Move to cell J4
From the PI menu select Insert Trend

Uncheck the Include all the cells in the array
Click the Cell Range containing data icon
Rev. 121908
Page 28

Start by selecting column A and B with the first row in which column B is not zero
Move to the end of the values in columns A and B

Click the add cells icon

Click Add
Rev. 121908
Page 29


Start by selecting column D and E with the first row in which column E is not zero
Move to the end of the values in columns D and E
Rev. 121908
Page 30


Click Add

Rev. 121908
Page 31

Start by selecting column G and H with the first row in which column H is not zero
Move to the end of the values in columns G and H

Click Add
Rev. 121908
Page 32

Click Next

Click Finish
Rev. 121908
Page 33

Review the TestSignal1, TestSignal2, and TestSignal3 trends.
Note: your instructor will review the results and explain the differences between
TestSignal1, TestSignal2, and TestSignal3
This lesson is complete
Rev. 121908
Page 34
Rev. 121908
Lesson 7
Configuring Performance Equations
What You Will Learn
How to use Performance Equations to perform server-side

recordable instance and summary calculations.
Performance Equations (PE) Functions

In addition to all the basic arithmetic operators, the PE subsystem provides a large number of
built-in functions that you can use to perform more complex operations, such as taking the sine
or cosine of a point value, taking the average of a tag's value over time, etc.
Function Arguments
Functions have one or more arguments, or inputs, which are enclosed in parenthesis following
the function name. Some of the arguments may be optional. If there are several arguments, they
are separated by commas:
functionName(argument1, argument2, argument3)
The following are examples of function expressions:

Max(3, 5, 12.6, 'sinusoid')
PrevEvent('sy:arc001', '*-2h')
Sqr(Abs(TagMax('tag', 'y', 't')))
Log(if 'tag'=2 then .5 else .2)
Functions can also be nested and joined in expressions:

Avg(TagVal('TagA', 'y'), TagVal('TagB', 'y'), TagVal('TagC', 'y') )
if TagVal('TagA', '*') < TagVal('TagB', '*') then sin('TagB') else sin('TagA')
You can use a tagname in any argument where a number or character string is called for. A
tagname in single quotes is evaluated as if it had been written TagVal(tagname), which is the
same as TagVal('tagname', '*' ). This gets the point's value at the "current" time for the
calculation. If the argument calls for a number, but the point's value is a digital state when the
function is evaluated, a run-time error (Calc Failed) is generated.
List of Built-in Functions by Type
The PE Scheduler provides a wide range of built-in functions that make it easier for you to
perform calculations on Historian data. These functions are discussed in detail in the PI Server
Application Userss Gude.
Math functions
Asin Arc sine
Acos Arc cosine
Atn Arc tangent
Atn2 Arc tangent (two arguments)
Cos Cosine
Cosh Hyperbolic cosine
Rev. 121908
Lesson 7 Configuring Performance Equations
Page 2
Exp Exponential
Log Natural logarithm
Log10 Common logarithm
Sin Sine
Sinh Hyperbolic sine
Sqr Square root
Tanh Hyperbolic tangent
Tan Tangent
Other Math Functions
Abs Absolute value
Float Conversion of string to number
Frac Fractional part of number
Int Integer part of number
Poly Evaluate polynomial
Round Round to nearest unit
Trunc Truncate to next smaller unit
Aggregate Functions
Avg Average
Max Maximum
Median Median selector
Min Minimum
PStDev Population standard deviation
SStDev Sample standard deviation
Total Sum
Miscellaneous Functions
BadVal See if a value is bad (not a number or time)
Curve Get value of a curve
DigState Get digital state from a string
IsDST Test whether a time is in local daylight savings time period
IsSet Test if a PI value is annotated, substituted, or questionable
StateNo The code number of a digital state
TagBad See if a point has an abnormal state
PI Archive Retrieval
NextEvent Time of a point's next Archive event
NextVal Point's next value after a time
PrevEvent Time of a point's previous Archive event
PrevVal Point's previous value before a time
TagVal Point's value at a time
PI Archive Search
FindEq Timestamp when point = value
FindGE Timestamp when point >= value
FindGT Timestamp when point > value
Rev. 121908
Page 3
FindLE Timestamp when point <= value

FindLT Timestamp when point < value
FindNE Timestamp when point ~= value
TimeEq Total period when point = value
TimeGE Total period when point >= value
TimeGT Total period when point > value
TimeLE Total period when point <= value
TimeLT Total period when point < value
TimeNE Total period when point ~= value
PI Archive
EventCount Number of Archive events
Statistics
PctGood Percent of good time in a period
Range Range of minimum to maximum value
StDev Time-weighted standard deviation
TagAvg Time-weighted average
TagMean Event-weighted average
TagMax Maximum value in a period
TagMin Minimum value in a period
TagTot Time integral over a period
Point Attributes
TagDesc Get a point's descriptor
TagEU Get a point's engineering unit string
TagExDesc Get a point's extended descriptor
TagName Get a point's name
TagNum Get a point's ID
TagSource Get a point's point source character
TagSpan Get a point's span
TagType Get a point's type character
TagTypVal Get a point's typical value
TagZero Get a point's zero value
Time Functions
Bod Timestamp for beginning of the day for given time
Bom Timestamp for beginning of the month for given time
Bonm Timestamp for first of the next month for given time
Day Day of the month from a time
DaySec Seconds since midnight from time
Hour Hour from a time
Minute Minute from a times
Month Month from a time
Noon Timestamp for local noon of day of a times
ParseTime Convert character string to time
Rev. 121908
Page 4
Second Second from a times

Weekday Day of the week from a times
Year Year from a time
Yearday Day of the year from a time
Dynamic Response
Arma Dynamic response from Auto Regressive Moving Average model
Delay Introduce time delay
MedianFilt Select the median value of time series
Impulse Dynamic response characterized by impulse response shape
Alarm StatusFunctions
AlmAckStat Alarm acknowledgement status code
AlmCondition Condition code number for Alarm State
AlmCondText Alarm condition as text
AlmPriority Alarm priority number
String Functions
Ascii ASCII character code for a character
Char String for ASCII character code(s)
Compare Wild comparison of two strings
DigText Text for a digital state
Format Formatting of a numerical number
InStr Instance of a sub-string
LCase Conversion of all characters to lower case
Len Length of a string
Left First characters in a string
LTrim Removal of blanks on the left side of a string
Mid Extraction of a sub-string from a string
Right Last characters in a string
RTrim Removal of blanks on the right side of a string
Trim Removal of blanks on both sides of a string
UCase Conversion of all characters to upper case
String Conversion
Concat Concatenate two or more strings
String String representing any PI value
Text Concatenation of strings for a series of PI value arguments
Rev. 121908
Page 5
Performance Equation Help File

PEReference.chm
Located in C:\Program Files\Rockwell Software\FactoryTalk Historian\Server\PIPC\HELP
Rev. 121908
Page 6
Editing Performance Equation Tags/Points with the SMT
Rev. 121908
Page 7
Performance Equation Scheduling

Performance Equations are from a separate Interface, different that the FactoryTalk Like Data
(FTLD) Interface. Since a completely different interface, it has its own configurations such as
scan classes. These configurations are controlled by a batch file named pipeschd.bat file located
in C:\Program Files\Rockwell Software\FactoryTalk Historian\Server\PI\bin
This file can be opened with the Interface Configuration Utility (ICU) and scan classes modified,
added and/or deleted.
Rev. 121908
Page 8
What's a Scan Class?

A scan class is a code that the PE Scheduler and other PI interfaces use for scheduling. Scan
classes always specify a period, which says how often to perform the calculation. Optionally,
scan classes can include an offset that specifies a start time for the calculations to begin and a
code that specifies that UTC time is used for the scheduling:
Period: The period specifies the interval between calculations. The first two digits are the hours,
the second two the minutes, and the third two the seconds. So, for example, the scan class can
specify that the calculation take place every hour (01:00:00), every three minutes (00:03:00),
every 52 seconds (00:00:52), and so on.
Offset: The offset specifies a start time for the calculation. The offset is optional. If no offset is
included in the scan class, the first calculation takes place immediately. The offset is counted
from midnight of the current day and, as with the period, the first two digits are the hours, the
second two the minutes, and the third two the seconds. So, for example, the offset can specify
that the first calculation occur at midnight (00:00:00), at 1AM (01:00:00), at 1PM (13:00:00), at
2:05PM (14:05:00), at 25 seconds past noon (12:00:25) and so on.
UTC Time Indicator: The UTC time indicator goes at the end of the scan class and is just a
comma followed by a capital U: (/f=08:00:00,07:00:00,U). When a scan class includes the UTC
time indicator, it means that the scheduling is with Universal Coordinate Time (UTC).
Note: If a scan class has a frequency of more than an hour, make it a UTC scan class, so that
your scheduling does not go out of sync after changes to or from daylight savings time. UTC
scan classes don't have this problem because they force the scan class scheduling to sync with
UTC, rather than local time.
Rev. 121908
Page 9
Exercise:
image:
3. Expand the Points category and select the Performance Equations plug-in:
4. Our first performance equation is going to be a Fahrenheit to Celsius conversion. Click on

the New toolbar button to begin creation of a new Performance Equation tag:
Rev. 121908
Page 10
5. On the General tab, set the following fields:

o Name:
T100_Demo_Temp_DegC
o Descriptor:
Tank T100 Temperature
o Point type:
Float32
o Eng Units:
Deg C
6. On the Equation tab, set the Equation to: (CDT158 -32) * 5/9
Click the Evaluate button just to make sure you dont get an error. Actual value will
differ:
7. On the Scheduling tab, change the radio button to Event-based scheduling. Change the
timestamp assignment option to timestamp of the triggering event. Use the
to select the tag: CDT158
button
Rev. 121908
Page 11
8. On the Archive tab, set the following fields:

o Exception Deviation:
0.25
o Compression Deviation:
0.5
o Compression Max Time:
15 Min
9. Click the Save toolbar button and check for a success message in the session record:
10. The next Performance Equation (PE) will combine two tank levels. Click on the New
toolbar button to begin creation of a new Performance Equation tag:

o Name:
BA:COMBINED_LEVELS
o Descriptor:
BA 1 & 2 Combined Levels
o Point type:
Float32
o Eng Units:
ft
Rev. 121908
Page 12
12. On the Equation tab, set the Equation to: BA:LEVEL.1 + BA:LEVEL.2
Click the Evaluate button just to make sure you dont get an error. Actual value will
differ:
13. On the Scheduling tab, change the Scan class to 3 which will cause the equation to be
calculated every 30 seconds:

0.25
0.5
15 Min
Rev. 121908
Page 13
16. The next PE will perform a totalizer summary calculation. We are going to pretend that the
T100_Demo_Temp.PV tag represents a flow rate in gallons per hour. Start by clicking the
New toolbar button to begin creation of a new Performance Equation tag:

o Name:
T100_Flow_1h_Total
o Descriptor:
Tank T100 One Hour Effluent Total
o Point type:
Float32
o Eng Units:
gal
Rev. 121908
Page 14
18. We want to totalize the T100_Demo_Temp.PV tag but only when at least 95% of the
readings are not suspect. On the Equation tab, set the Equation to the following
(Hintuse the
button when appropriate to search for tags to fill in your equation,
rather than typing the tag names in from scratch):
if pctgood(InstaCorp.InstaSoap.Mixing:RSLinx
InstaCorp.InstaSoap.Mixing:RSLinx
Enterprise:CLX1.T100_Demo_Temp.PV, *-1h, *) > 95 then
Enterprise:CLX1.T100_Demo_Temp.PV
tagtot(InstaCorp.
Enterprise:CLX1.T100_Demo_Temp.PV,
Enterprise:CLX1.T100_Demo_Temp.PV *-1h, *) * 24 else 0
Notice the multiplication by 24 to convert into a per day value which FactoryTalk Historian
needs. Click the Evaluate button to make sure you dont get an error. Actual result will
differ:
calculated every 2 minutes:
Rev. 121908
Page 15

0.25
0.5
15 Min
22. The last PE will totalize the amount of time that CDM158 is in the manual state. Start by
clicking the New toolbar button to begin creation of a new Performance Equation tag:
Rev. 121908
Page 16

o Name:
CDM158_Manual_Percent
o Descriptor:
Percent of time in manual mode over last hour
o Point type:
Float32
o Eng Units:
min / hr
24. On the Equation tab, set the Equation to:

timeeq(cdm158, *-1h, *, manual) / 36
Notice the single quotes for most parameters but the double-quotes for the string literal. Click
the Evaluate button to make sure you dont get an error. Actual result will differ:
calculated every 2 minutes:
Rev. 121908
Page 17

o Typical value:
50
o Zero:
0
o Span:
100
o Step:
Off
0.25
0.5
o Exception Max Time:
10 Min
15 Min
28. We want to watch some of our new Performance Equation tags. Expand the Data category
and select the Current Values plug-in:
Rev. 121908
Page 18
29. Use the Tag Search button (possibly repeatedly) to select the following tags:
o BA:COMBINED_LEVELS
o BA:LEVEL.1
o BA:LEVEL.2
o CDM158
o CDM158_Manual_Percent
o InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Temp.PV
o T100_Demo_Temp_DegC
o T100_Flow_1h_Total
30. Click the Start Updating button to watch the relationship between the tags:
31. Close the SMT, this exercise is finished.
Rev. 121908
Lesson 8
Configuring Totalizers
What You Will Learn
How to use Totalizers to perform server-side recordable

instance and summary calculations.
Historian TOTALIZER SUBSYSTEM

The Historian Totalizer Subsystem (Totalizer) performs common calculations such as totals,
averages, minimum and maximum values, and standard deviations. Output of a calculation is
stored in a Historian point.
The main difference between a Performance Equations point and a Totalizer point calculating the
same summary is that Totalizer calculates from realtime inputs (as opposed to archived values.)
Performance Equations are based on Archive events, while Totalizer results are based on
Snapshot events.
Historian Totals are the most accurate way to represent production summary data. Totalizers can
be started and reset based on time and event, and ensure the highest accuracy in the calculation
of flow volumes and other critical variables used to monitor product transfers or production
performance. Totalizer is especially practical for totaling measurements or other process
variables at the end of specific time periods, such as the end-of-day yields.
Totalizer Subsystem Overview
Totalizer allows you to perform certain calculations on a point in the Snapshot, and to store the
results in another point. The process is called postprocessing. Postprocessing includes the
following types of summary calculation:
Total
Average
Minimum
Maximum
Range
Standard Deviation
Median
Additionally, Totalizer permits the counting of update events for a point. The types of counting
allowed are as follows:
All Events
Event Equal To a value
Event Not Equal To a value
Event Greater Than a value
Event Greater Than or Equal To a value
Event Less Than a value
Event Less Than or Equal To a value
Event change from Greater Than or Equal To to Less Than
Event change from Less Than to Greater Than or Equal To
Rev. 121908
Lesson 8 Configuring Totalizers
Page 2
The Totalizer is a dedicated subsystem, pitotal. This subsystem signs up for exceptions, which
means that it is notified when a new value is added to the Snapshot for any of the points to be
postprocessed. After postprocessing, values, for example, average, total, or time in state, are
sent back to the Historian Snapshot.
Totalizer vs. Performance Equations
Totalizer may be more accurate because the values used in Totalizer calculations are taken from
the Snapshot, not after the application of compression as in the case of Performance Equations.
Additional details can be found in the Historian SE Server Application Userss Gude.
Rev. 121908
Page 3
Exercise:
image:
3. Expand the Points category and select the Totalizers plug-in:
4. Our first Totalizer is going to be a a T100_Flow_1h_Total tag. We are going pretend that
T100_Demo_Temp.PV represents a flow rate in gal / hour which we want to totalize over
the preceding hour every two minutes. Click on the Create a new Totalizer toolbar
button to begin:
Rev. 121908
Page 4
5. On the Name & Type tab, set the following fields:

o Name:
T100_Flow_1h_Tot
o Descriptor:
Tank T100 One Hour Effluent Total
o Source Tag:
Enterprise:CLX1.T100_Demo_Temp.PV
o Point type:
Float32
o Eng Units:
gal
o Totalizer Type: Moving Time Weighted Total
6. DO NOT reproduce what you see in the following image. If we wanted to precisely emulate
the Performance Equations configuration of writing a total every two minutes, on the
Sampling tab we would select to Periodically sample Interpolated values every 2
Minutes (again, do not make these selectionsjust for informational purposes).
Rev. 121908
Page 5
7. Instead, we can achieve much more precise results by choosing to sample Whenever a new
source tag event occurs (Natural). Use this settings on your Sampling tab:
8. On the Results tab, set the following fields:

o Write final results:
after a time period elapses
o Results every:
1 Hour(s)
Rev. 121908
Page 6

o Typical Value:
50
o Zero:
0
o Span:
100
0.25
0.5
15 Min
10. On the Options tab, set the following fields:

o Conversion Factor:
24.0
o Pct good values needed: 95
Rev. 121908
Page 7
12. The next Totalizer will reproduce the calculation from the CDM158_Manual_Percent
performance equation. Click on the Create a new Totalizer toolbar button to begin:
o Name:
CDM158_Manual_Pct
o Descriptor:
Percent of time in manual mode over last hour
o Source Tag:
CDM158
o Point type:
Float32
o Eng Units:
%
o Totalizer Type: Count Events, Time when TRUE, Moving, equal to, Manual
14.
On the Sampling tab, select Whenever a new source tag even occurs (Natural):
Rev. 121908
Page 8

after a time period elapses
o Results every:
1 Hour(s)

o Typical value:
50
o Zero:
0
o Span:
100
o Step:
Off
0.25
o Compression Deviation: 0.5
o Compression Max Time:15 Min
Rev. 121908
Page 9
17. On the Options tab, set the following fields:

o Conversion Factor:
0.02777
o Pct good values needed: 95
19. The last Totalizer will perform a block average on the BA:LEVEL.1 tag:
Rev. 121908
Page 10
o Name:
BA:LEVEL1.STEPAVG
o Descriptor:
BA:LEVEL.1 one minute block average
o Source Tag:
BA:LEVEL.1
o Point type:
Float32
o Totalizer Type: Summary, Block, Time Weighted, Average
21.
On the Sampling tab, select Whenever a new source tag even occurs (Natural):
Rev. 121908
Page 11

after time period elapses
o Results every:
1 Minute(s)
o Write interim results: stamped one second after start

o Typical value:
50
o Zero:
0
o Span:
100
o Step:
On
0
o Exception Max Time: 0
o Compressing:
Off
Rev. 121908
Page 12
25. We want to watch some of our new Totalizer tags. Expand the Data category and select
the Current Values plug-in:
26. Use the Tag Search button (possibly repeatedly) to select the following tags:
o BA:LEVEL1.STEPAVG
o BA:LEVEL.1
o CDM158
o CDM158_Manual_Pct
o CDM158_Manual_Percent
o InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Temp.PV
o T100_Flow_1h_Tot
o T100_Flow_1h_Total
27. Click the Start Updating button to watch the relationship between the tags:
28. Close the SMT, this exercise is finished.
Rev. 121908
Lesson 9
Configuring Event Triggered Reads
What You Will Learn
How to configure event Triggered Reads
Factorytalk Historian tags can be configure to be read in polled or advised modes. In

general, if polled, tags would be read every certain time interval (like once per second). If
advised, a change in that tags value will trigger a read. In this exercise, you will examine
event triggered reads which take place only when a specific change is detected in a separate,
triggering tag.
Event triggered reads can be configured to operate in one of four modes:
Anychange
Increment
Decrement
Nonzero
Rev. 121908
Lesson 9 Configuring Event Triggered Reads
Page 2
Exercise Part A
In our first contrived example, assume that you have a batch process comprised of three phases
(1, 2, and 3). There is also a zero (0) phase that indicates the process is in a stopped state.
Phases progress in order from 0 to 3 and back to 0. In this scenario, you have a process variable
that you want to record at the beginning of every running state. To accomplish this, you are
going to use the Increment event trigger mode. You might think that you could accomplish the
goal equally well with the Nonzero mode. However, Anychange and Nonzero modes will
trigger when the snapshot receives an identical value with an updated timestamp and you only
want one record at the beginning of the phase.
In this first section, you will configure the collection of the phase indicator which will be the trigger.
image.
2. Launch the FactoryTalk Administrator Console.
3. Select Network directory, then click OK.
4. In the FT Administrator console explorer, right-click InstaCorp, and click Add Individual
Historian Points
Rev. 121908
Page 3
5. Set the data collection interface to FTLD2, set the scan class for new point to 1 second and
click Browse Tags.
6. Browse InstaSoap \ Mixing \ CLX1 \ Online and select the tag: T100_Phase_Counter.ACC
7. Click Add Tags(s) to List, (selected tag will be displayed in the lower window) and click
OK.
#1
#2
#3
#4
Rev. 121908
Page 4
8. Click OK.
Note: The new tag just added to the FT Historian will have the name
InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Phase_Counter.ACC
In this second section, you will configure collection of the start of phase parameter. This parameter
will actually be the tank volume which you will assume is not already being collected all the time.
2. Expand the Points category and select the Point Builder plug-in.
Rev. 121908
Page 5
3. Using the Point Builder SMT plug-in, click on the Search toolbar button.
4. Enter a Tag Mask of *T100* and then click the Search button.
5. Select tag: InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Volume.PV
6. Click OK.
Rev. 121908
Page 6
7. Highlight the entire name and overtype a new name of: T100_Phase_Start_Vol
8. Set the Exdesc (Extended Descriptor) field to the following. Note: EVENT must be
UPPERCASE!:
EVENT='InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Phase_Counter.ACC' Increment
9. Select the Archive Tab and configure the following attributes:

Compressing off
Exception testing off by setting Exception Deviation and Exception Max Time both to zero
Rev. 121908
Page 7
10. Select the Classic tab.

11. Set Location 3 to 0 (to identify as Polled or Event Trigger Input point).
12. Click the Save button on the toolbar.
13. Expand the Data category and select the Current Values plug-in.
14. Using the Current Values SMT plug-in, click on the Search toolbar button.
Rev. 121908
Page 8
15. Enter a Tag Mask of *T100* and click the Search button.
16. Select the following tags:
InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Volume.PV
T100_Phase_Start_Vol
17. Click OK.
18. Using the Current Values SMT plug-in, click the Start Updating toolbar button.
19. While the phase counter stays the same, observe the following:
T100_Demo_Volume.PV changes
T100_Phase_Start_Vol remains at its previous value
Rev. 121908
Page 9
20. When the phase counter increments, observe the following:

T100_Phase_Start_Vol is set equal to T100_Demo_Volume.PV
21. When the phase counter rolls over from 3 to 0, observe the following:
T100_Demo_Volume.PV changes
T100_Phase_Start_Vol remains at its previous value and does not get updated
Part B
In our second example, you will assume you have a reserve coolant tank. When the tank is being
depleted, you want to correlate the temperature of an exothermic reactor vessel. When the
coolant tank is being filled or is steady-state, you are unconcerned with the tank temperature. In
this example, you will use the Decrement mode. For this part of the exercise, you will pretend
that you are not already collecting the tank temperature all the time.
2. Using the Point Builder SMT plug-in, click the Search toolbar button.
Rev. 121908
Page 10
3. Enter a Tag Mask of *T100* and then click the Search button.
4. Select tag: InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Temp.PV
5. Click OK.
6. Highlight the entire name and overtype a new name of: T100_Draining_Temp
7. Set the Exdesc (Extended Descriptor) field to the following. Note: EVENT must be
UPPERCASE!
EVENT='InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Volume.PV' Decrement
Rev. 121908
Page 11

9. Set Location 3 to 0.
Visualize the tags from examples 1 and 2 to see if they are working correctly
using ProcessBook by following these steps:
1. Launch ProcessBook.
2. Create a new display by clicking the new button on the toolbar.
Rev. 121908
Page 12
3. Select the type as ProcessBook Display (.pdi) File and give it the name Event Triggered
Read.
4. Click OK.
5. Verify that you are in build mode by checking the build mode icon on the toolbar. It will be
highlighted (if not, click the build mode icon to change to build mode).
7. Drag a Trend on the Event Triggered Reads display that covers most of the empty space.
Rev. 121908
Page 13
8. The Define Trend dialog will appear. Select the Tag Search button.
9. Select the Tag Mask to *T100* and click Search.

10. Select the following two tags:
T100_Phase_Start_Vol
11. Click OK.
Rev. 121908
Page 14
12. Rename Plot-0 to Phase Increment

13. Set the Scale radio button to Multiple Scales.
14. Set the Plot Time Start to *-5m.
15. Click on the New Plot button.
#4
#1
#2
#3
Rev. 121908
Page 15
16. Rename Plot-1 to Volume Decrement.

17. Use the Tag Search button to select the following two tags:
InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Volume.PV
T100_Draining_Temp
18. Set the Scale radio button to Multiple Scales.

#1
#2
#3
#4
20. On the Display Format tab, check the Markers checkbox.
Rev. 121908
Page 16
21. In the Plot drop-down box, select the Phase Increment plot.
22. Check the box for Markers.
23. Click OK.
24. Ignore any message about too many data points for markers.
25. If necessary, select the Run button on the ProcessBook toolbar.
Rev. 121908
Page 17
26. Discuss the results with your fellow students and instructor.
Rev. 121908
Page 18
This page is intentionally left blank
Rev. 121908
Lesson 10
Configuring Basic Output Points
What You Will Learn
How to configure an outpoint point using the source tag

method
In this exercise, you are going to look at FactoryTalk Historians basic output point capabilities.
This capability should be avoided for real-time control purposes where an HMI using a
FactoryTalk Live Data connection is much more appropriate. It is useful for scenarios where
complex calculations are performed by FactoryTalk Historian and the results are handed back to
the HMI or control system for possible further action.
This exercise will specifically explore a scenario where you have a tank effluent stream which is
being discharged back into a local river. Government regulations do not regulate the spot
temperature of the effluent, but they do set restrictions based on the 5 minute time-weighted
average of the effluent temperature. Extra stream processing must be performed when the 5
minute time-weighted average exceeds 106 degrees. Because the time-weighted average
calculation is more sophisticated than you are comfortable programming in the controller,
FactoryTalk Historian will take care of this calculation and pass the result back to the controller
for further action.
Reference:
Output Tags
Set location 3 = 2 for output mode

Source Tag specifies the source of the data to be sent.
Instrument Tag specifies the destination of the Source Tag value
Data transfer is triggered when Source Tag value changes and snapshot entry updated
Rev. 121908
Lesson 10 Configuring Basic Output Points
Page 2
In the first part of this exercise you will configure a totalizer to perform the time-weighted average
calculation.
1. Verify that you are on the VM-HIST-1 image by checking the hostname on the background image.
3. Expand the Points category and select the Totalizers plug-in.
4. Using the Totalizers SMT plug-in, click on the Create a new Totalizer toolbar button.
5. Set the totalizer Name: T100_TWA_Temperature

6. Click the tag search button to the right of the Source Tag.
7. Enter a Tag Mask of *T100*.

8. Click the Search button.
Rev. 121908
Page 3
9. Select tag: InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Temp.PV

10. Click OK.
11. Verify the above selected Source Tag.

12. Under the Name & Type section, set the following:
Change the Summary Calculation from Block to Moving

Change the Summary Calculation from Total to Average
Rev. 121908
Page 4
13. Select the Results Tab.

14. Under the Details section, set the Results every to 5 Minute(s).
15. Select the Archive tab and configure the following attributes:
Exception Deviation to 0
Compression Deviation to 0.1
Exception Deviation Max Time to 0
Set the Compression Max Time to 15 Minutes
17. Minimize the SMT.
Rev. 121908
Page 5
In the next section you are going to configure the output point for data collection to automate the
configuration of most of the parameters. Later, you will change it from data collection to output
mode.
1. Launch the FactoryTalk Administrator Console.
2. Select Network directory, then OK.
3. In the FT Administrator console explorer, right-click InstaCorp, and click Add Individual
Historian Points
4. Set the data collection interface to FTLD2.

5. Set the scan class for new point to 1 second.
6. Click Browse Tags.
Rev. 121908
Page 6
7. Browse InstaSoap \ Mixing \ CLX1 \ Online and select the tag T100_TWA_Temp
8. Click Add Tags(s) to List, (the selected tag will be displayed in the lower window).
9. Click OK.
10. Click OK.
Note: the new tag just added to FT Historian will have the name
InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_TWA_TEMP
11. Close the FactoryTalk Administration Console.
Rev. 121908
Page 7
In the next section you will modify the newly configured tag to be used for output instead of
input.
1. Return to the minimized SMT application.
2. Expand the Points category and select the Point Builder plug-in:
3. Using the Point Builder SMT plug-in under the Points category, click on the Search toolbar button.
Rev. 121908
Page 8
4. Enter a Tag Mask of *T100*

6. Select tag: InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_TWA_Temp
Note: Do not accidentally load the similarly named T100_TWA_Temperature totalizer.
7. Click OK.
Rev. 121908
Page 9
8. Verify the previously selected tag name.
9. Use the Tag search
button next to the Source tag field.
10. Select the tag:
T100_TWA_Temperature
11. Click OK.

13. Change Location3 to 2. This configures this tag as an Output tag. Whenever the value in the
Source Tag field changes (the Totalizer tag, T100_TWA_Temperature), it will be sent to the
Instrument Tag (T100_TWA_Temp in CLX1).
Rev. 121908
Page 10
The time-weighted average values should now be written down to the controller. To verify, you are
going to use the Rockwell Software Data Client to read the value from the controller.
1. Launch the Rockwell Software data client: Start > All Programs > Rockwell Software >
FactoryTalk Tools > Rockwell Software Data Client
2. Select FactoryTalk:
3. Select Network and click OK.
Rev. 121908
Page 11
4. Expand $Global, select InstaCorp and click OK:
5. Change the Update Rate to 1000 ms and click OK.
6. Expand the tree InstaCorp InstaSoap Mixing - CLX1 and click Online.
7. In the right-hand view, click on theT100_TWA_Temp tag.
8. Click OK.
#3
#1
#2
Rev. 121908
Page 12
9. Verify that the value is being updated regularly.
Rev. 121908
Lesson 11
Using Data Collection with Handshaking
What You Will Learn
Configure polled tags to be read based on a event

Calculate a checksum using a performance equations
Use the checksum as the trigger and value for a output tag
Review and confirm that the PLC Logic completes the
handshake
Part A - FactoryTalk Historian SE PLC Handshaking

The purpose of this Lesson is to give an example of how to setup a simple handshaking routine
to verify that the PLC can communicate with the FactoryTalk Historian SE Server to the
snapshot level. If the handshaking routine fails within the allotted time, a handshaking fault is
set in the PLC and can be reported to an HMI alarm system.
Once enable the PLC starts the handshake to the FTH SE Server as follows:
FTH_HS_Timer is done
FTH _HS_Counter is incremented
FTH_HS Error_Timer is started
FTH_HS Counter accumulated value is move into FTH_HS_TO_HIST value
The change in the FTH_HS_TO_HIST value is sent to the FTH SE Server
The FTH_HS_TO_HIST value is both the trigger and the value for the
FTH_FROM_HIST output tag
The output tag is written to the PLC
The PLC Logic compares the value sent and the value returned and is they are equal and
resets the Handshake logic. If they are not equal and the FTH_HS Error_Timer times
out a Handshake fault is set and the Handshake logic is reset.
The Handshake routine will restart when the FTH_HS_Timer is done
Rev. 121908
Lesson 11 Using Data Collection with Handshaking
Page 2
PLC Handshaking Logic
Rev. 121908
Page 3
FTH SE Tag Terms
Instrument Tag is the data source for advised and polled tags and is the destination for
output tag
Source Tag is both the trigger and the value for a output tag
FTH SE Tags
There are two FTH SE tags required to complete this handshaking routine;
FTH_HS_TO_HIST is an advised tag. It has its exception value set to 0 (all changes
are sent to the snapshot) and its compression value set to 0 (all non duplicate changes
are sent to the archive)
FTH_FROM_HIST is a output tag (location 3 set to 2) with exception value is set to 0
(all values are sent to the PLC) and its compression value turned off. Its source tag is
FTH_HS_TO_HIST (which is both its trigger and value).
Note: The compression for FTH_HS_TO_HIST could be turned on if you want to archive
all the handshake values sent to the PLC
Rev. 121908
Page 4
Configure FTH SE Handshaking

Verify that you have the VM-HIST-1 VMWare image selected

Note: Your instructor will provide you with the correct path
Open Windows explorer and select the FTH_Handshaking.xls file
Double click on the select file to open
Rev. 121908
Page 5

From the PI-SMT menu select Export Tags

Verify that the Mode is set to Create
Click OK
Rev. 121908
Page 6

Verify that the tags were created with out any errors
Click OK
Close Excel

From the Start menu open the System Management Tools
Rev. 121908
Page 7

From the Points folder select Point Builder


In the Tag Mask enter *HS*
in the Point source enter FTLD
click Search
Rev. 121908
Page 8

Select the FTH_HS_FROM_HIST and FTH_HS_TO_HIST tags
Click OK

Select the FTH_HS_FROM_HIST tag
Select the Source Tag icon
Rev. 121908
Page 9

In the Tag Mask enter *HS*
In the Point source enter FTLD
Click Search

Select the FTH_HS_TO_HIST tag
Click OK

Verify that the FTH_HS_FROM_HIST tag is still selected
Click the Save icon
Rev. 121908
Page 10

Select the VM-CLX VMWare image

From the Start menu open RSLogix 5000
Go online with the FTHistorian processor (slot 3)
Verify that the Handshaking logic is turned on (rung 10)
Verify that the FTH_HS_Timer is running and resetting

Verify that the FTH_HS_TO_ HIST and the FTH_HS_FROM_HIST are equal
and that the handshaking logic is working
In this example, the FTH_HS_TO_ HIST tag in the ControlLogix processor is automatically
changing based on the accumulated value of a counter. Since this is an Advised tag in
FactoryTalk Historian, whenever the value changes Historian is reading the value and archiving.
FactoryTalk Historian is handshaking with the ControlLogix processor by sending the same
value back to ControlLogix in tag FTH_HS_FROM_HIST. The handshaking logic in the
ControlLogix program is comparing the two values, verifying that the value sent to
FactoryTalk Historian is the same value that was sent back. If these values do not match, the
FTH_HS Error_Timer timer times out, resetting the logic. Additional ladder logic could be
written to set off some other alarms, effect machine or process operation in some way, etc.
This Part A exercise is complete
Rev. 121908
Page 11
Part B - FactoryTalk Historian SE Configuration for an Event Read

with Checksum Handshaking
This example, for training purposes only, will use an event to read 5 tags. The PLC will
calculate a simple AND checksum on the 5 data points and store that checksum in a tag called
Checksum1. The FactoryTalk Historian (FTH) SE will use a performance equation tag to
calculate the same AND checksum. The performance tag (FTH_Server_CheckSum) will be
the Source Tag for the output tag FTH_Event_Write which will write that value to the PLC tag
FTH_Event_Write
The PLC program will compare the value FTH_Event_Write to the Checksum1 value and if
they are equal will reset the Event Read logic. If they are not equal or the Event_Read_Timer
times out then a fault is set.
Rev. 121908
Page 12
FTH Event Read Logic
Rev. 121908
Page 13
Create FTHistorian Event Read Tags

Select the VM-HIST-1 image
2. Do the following Steps:

From the Start menu select Microsoft Office Excel 2003
Rev. 121908
Page 14

From the File menu select Open

Note: Your instructor provide the path to the FTH_Class_Files
Select the FTH_Event_Read_Tags.xls file
Click Open
Rev. 121908
Page 15

From the PI-SMT menu select Export Tags

Verify that the Mode selected is Create
Click OK
Rev. 121908
Page 16
Configure a Performance Tag FTH_Server_CheckSum


Expand the Points folder
Select Performance Equations
Rev. 121908
Page 17

Click the New icon

Select the General tab
In the Name textbox enter FTH_Server_CheckSum
In the Point type combo box select Int32
select the Equation tab

Select the Tag Search icon
Rev. 121908
Page 18

In the Tag Mask textbox enter *FTH*
In the Point Source textbox enter FTLD
Click Search

Select the VM-HIST-1 FTH_Data_HS tag
Click OK

Press the Space bar
Enter and
Press the Space bar
Rev. 121908
Page 19

Select the VM-HIST-1 FTH_Data1 tag
Click OK

Press the Space bar
Enter and
Press the Space bar

Click OK
Rev. 121908
Page 20

Press the Space bar
Enter and
Press the Space bar

Click OK

Press the Space bar
Enter and
Press the Space bar
Rev. 121908
Page 21

Click OK

Select the Scheduling tab
Click the Tag Search icon

Select VM-HIST-1 FTH_Data_HS
Click OK
Rev. 121908
Page 22

Select the Archive tab

Set the Exception Deviation options as indicated below
Set the Compression Deviation options as indicated below
Set the Compressing options as indicated below
Rev. 121908
Page 23

Select the General tab
Click the Save icon
Configure FTH_Event_Write Tag

Note: The System Management Tools may already be open
Rev. 121908
Page 24

Select Point Builder


Click Search
Rev. 121908
Page 25

Select VM-HIST-1 FTH_Event_Write tag
Click OK

Select the VM-HIST-1 FTH-Event-Write tag
Click the Tag Search icon
Rev. 121908
Page 26

In the Point Source textbox enter C
Click Search

Select VM-HIST-1 FTH_Server_CheckSum tag
Click OK
Rev. 121908
Page 27

Verify that the Source tag textbox contains the tag FTH-Server_CheckSum
Click the Save icon
Configure Event Read Tags

Rev. 121908
Page 28

Select Point Builder


Click Search
Rev. 121908
Page 29

Select the VM-HIST-1 FTH_Data1, FTH_Data2, FTH_Data2, FTH_Data4 and
FTH_Data_HS Tags
Click OK

Select the FTH_Data1 tag
In the Exdesc: text box enter EVENT=FTH_Event_Read Increment
Notes:
1. Be sure to use EVENT in uppercase (event will not work!)
2. You may want to copy this string to clipboard for use in the additional steps
that follow
Click Save
Rev. 121908
Page 30

In the Exdesc: text box enter EVENT=FTH_Event_Read Increment (or paste
from clipboard)
Click Save
Rev. 121908
Page 31

from clipboard)
Click Save
Rev. 121908
Page 32

from clipboard)
Click Save
Rev. 121908
Page 33

Select the FTH_Data_HS tag
from clipboard)
Click Save
Rev. 121908
Page 34

Note: The FTH_Data1, FTH_Data2, FTH_Data3, FTH_Data4 and FTH_Data_HS
tags all have the same Archive settings
1. Review the Archive settings

Note: The FTH_Data1, FTH_Data2, FTH_Data3, FTH_Data4 and FTH_Data_HS
tags all have the same Classic settings, except for Instrument Tag which will be
unique per tag.
Review the Classic settings
Rev. 121908
Page 35
Enable the Event Read Logic and Verify the Results

Select the VM-CLX image

From the Start menu select RSLogix 5000

From the Communications menu select Who Active
Rev. 121908
Page 36

Select the FTHistorian processor
Click Go Online

Click Select File
Rev. 121908
Page 37

Select the FTHistorian1.ACD file
Note: Check with your instructor for the path to this file
Click Select

If prompted click Upload
Rev. 121908
Page 38

Double click on the Program Tag

In the FTH_Data1 Value text box enter 40
Rev. 121908
Page 39

Double click on the MainRoutine

Goto Rung 20
Select the FTH_Start_Event_Read bit
Right mouse click and select Toggle Bit
Note: If the bit is on you will need to toggle it off and the toggle it on
Rev. 121908
Page 40

Repeat steps 9 - 10 11 and enter different values FTH_Data1, 2, 3, 4
Verify the Event Read Using the System Management Tool


Expand the Data folder
Select Recorded Values
Rev. 121908
Page 41


Click Search
Rev. 121908
Page 42

Select the VM-HIST-1 FTH_Data1, FTH_Data2, FTH_Data3 and FTH_Data4
tags
Click OK

Select FTH_Data1
Click Get Events
Rev. 121908
Page 43

Verify that the values you enter were Archived
Note: Your values may be different from the valus in the screen shot

Repeat steps 6 & 7 for FTH_Data2, FTH_Data3 and FTH_Data4
This Lesson is Complete
Rev. 121908
Page 44
Rev. 121908
Lesson 12
Understanding and Using Basic Alarms
What You Will Learn
How to configure server side basic alarms

Using ProcessBook Trend and AlarmViewer to view
alarms
In this exercise you will examine alarming capabilities using FactoryTalk Historians server-side.
In the basic output points exercise, you looked at how you might take advantage of FTHs more
advanced calculation capabilities to enable the control system to alarm off of a time-weighted
average (TWA). This exercise contains more complex alarm conditions which are better handled
at the server instead of the controller.
Rev. 121908
Lesson 12 Understanding and Using Basic Alarms
Page 2
The first part of this exercise incorporates changes in government regulations addressed in
the basic output points exercise. Originally, additional effluent processing was required
when the 5 minute time-weighted average exceeded 106 degrees. Our company, having
noticed that the 106 degree mark is occasionally only briefly crossed, has successfully
lobbied the government to loosen their restrictions. Now mandatory effluent processing is
required when the 5m TWA exceeds 108 or when the 5m TWA exceeds 106 degrees for at
least one full minute. While these new regulations will result in cheaper operations, they
are becoming increasingly difficult to handle in the control system. You will employ
FactoryTalk Historians alarming capabilities to better handle these new restrictions.
image.
2. Open the FactoryTalk Administration Console and right-click on the Mach3 Area of Line1
of the Application MyApp. Select Add Individual Historian Points
Rev. 121908
Page 3

Select the Program:MainProgram
Select StoreValue_1 and StoreValue_2 tags (use control-click to select both)
Click OK
4. Click OK on dialog that follows to add these tags to Historian.

Rev. 121908
Page 4
6. All alarm points must belong to an existing alarm group. Expand the Alarms category and
select the Alarm Groups plug-in.
7. If a dialog box pops up, click OK to confirm the default alarm point sources. Notice the
@ symbol will be used for PI Alarm Points:
8. In the center window, select the VM-HIST-1 server icon.

9. Click the Create a new Alarm Group toolbar button.
Rev. 121908
Page 5
10. Set the Group Name field to Environmental and the Descriptor field to Group for
Environmental Alarms.
11. Click OK.
13. Using the Point Builder SMT plug-in, click on the New toolbar button.
14. Name the tag T100_TWA_Temp_Alarm (NOTE: Do not Save this tag until you at least
change the Point class (in following steps) to Alarm. Once you save a tag you cannot
change its Point class).
Rev. 121908
Page 6
15. In the General Tab, configure the following parameters:
Point class: Alarm
Point source: @
Point type: Digital
Digital set: pialarm33
Exdesc to the alarm group: Environmental
16. Click the source tag Search
button to the right of the Source tag field
17. Enter a Tag Mask of *Store* and then click the Search button.
18. Select tag StoreValue_1, as the Source Tag and click OK.
19. Verify that the following options were set in Step 14 to 18 above.
20. Click the Alarm tab.
Rev. 121908
Page 7
21. Configure the following Alarm tab parameters:
23. Minimize SMT.

24. The value of the T100_TWA_Temp_Alarm tag can be monitored in the Current Values
plug-in or in a ProcessBook display. Ideally, you would configure an output point to use this
alarm as its source so the control system could take appropriate action based on its state.
HIGH or HIHI being sent to the control system based on the value of the tag being
monitored.
25. We will use ProcessBook trend to display the value and alarm status. Launch ProcessBook.
.
26. Click the New button on the toolbar.
Rev. 121908
Page 8
27. Select the type of ProcessBook Display (pdi) file and enter T100 TWA Temp Alarm in the
Display Name field. Click OK.
28. Verify that you are in build mode, the build mode icon on the toolbar will be highlighted (if
not, click the build mode icon to change to build mode).
30. Drag a Trend box into the T100 TWA Temp Alarm display that covers most of empty space.
Rev. 121908
Page 9
31. The Define Trend view will appear, select the Tag Search button.
Rev. 121908
Page 10
32. Use the Tag Search feature (maybe more than once) to select the following two tags:
T100_TWA_Temp_Alarm
MyApp.Line1.Mach3:Mach3_Ent:FTHistorian.Program:MainProgram.StoreVa
lue_1

34. Set Scale to Multiple Scales.
35. The Define Trend dialog box should now be configured as follows. Click OK.
Rev. 121908
Page 11
37. We now will manually change the value of the StoreValue_1 tag in the CLX processor to
simulate values that will trigger alarm conditions. Open the Data Client tool from Start ->
All Programs -> Rockwell Software -> FactoryTalk Tools:
38. If requested, on the Initial Connection dialog box select FactoryTalk and then on the
Select FactoryTalk Directory dialog box select Network Connection and click the OK
button(s):
Rev. 121908
Page 12
39. Select Mach3 of Line1 of the MyApp application and click OK:
40. Click OK on the following dialog:
Rev. 121908
Page 13
41. Select the StoreValue_1 tag in the Program:MainProgram location and click OK:
42. Right-click on the tag and select Async Write:
Rev. 121908
Page 14
43. Type in a value of 100 and then click OK:
44. In the Data Test Client, you should see the value of 100 is now in the CLX tag. If you go
back to your ProcessBook trend, you should see the trend updated with a value of 100 for this
tag.
Rev. 121908
Page 15
45. The alarms you set up will be triggered with a HIGH alarm if the value of the
StoreValue_1 tag is greater than 106 for more than a minute. A HIHI alarm will be
triggered if the value is greater than 108 at all (doesnt have to be for a minute). Using the
Test client, experiment with changing the value of StoreValue_1 and seeing the results on
your trend. You should see results similar to the following:
Rev. 121908
Page 16
Some time after the changes to the regulations took affect, the Green&Clean activist group
successfully lobbied the government to make them aware of the tragic die off of
Helicobacter pylori, an endangered bacterium. It turns out that when the rivers
temperature changes too quickly, this whole family of bacteria is unable to adapt. The
government has consequently added an additional restriction to the effluent stream
temperate. If the spot temperature changes faster than 80 degrees per second, additional
processing must be performed.
1. Unfortunately you cannot reuse the existing alarm point for this new regulation because it is
dependant on a different source tag. Select the Point Builder plug-in under the Points
category.
3. Name the tag T100_Temp_Rise_Alarm.

4. From the General Tab, configure the following parameters:
Point class: Alarm
Point source: @
Point type: Digital
Digital set: pialarm33
Exdesc to the alarm group: Environmental
5. Click the source tag Search

button to the right of the Source tag field and select the
StoreValue2 tag that you brought into Historian earlier.
6. Verify the following options.
Rev. 121908
Page 17
7. Click the Alarm tab

8. Configure the Alarm tab parameters as follows:
Rev. 121908
Page 18
12. Use the Search tool (maybe more than once) to select the following tags:
lue_1
lue_2
T100_TWA_Temp_Alarm
T100_Temp_Rise_Alarm
13. Using the Current Values SMT plug-in, click on the Start Updating toolbar button.
14. As you did earlier in this exercise, use the Data Test Client to change the values of the
StoreValue_1 and StoreValue_2 tags. Observe the Current Values for each tag and the
Alarm tags in the SMT. The T100_TWA_Temp_Alarm should be going to HIGH if
StoreValue_1 is greater than 106 for more than a minute and HIHI if at all greater than
108. The T100_Temp_Rise_Alarm should be displaying RATE if the change of the
StoreValue_2 is greater than 80 per second.
Finally in the third part of this exercise you are going to look at visualizing these alarms
with the separately licensed AlarmViewer utility.
1. Launch the PI AlarmViewer either from the icon on the desktop (if present) or from
location:
Start -> All Programs -> PI System -> PI AlarmViewer.
2. If you get a connection error, click OK
Rev. 121908
Page 19
3. In the Displayed Servers pane (lower-right corner of screen), place a check in the box next
to VM-HIST-1.
4. In the Alarm Groups pane on the left, select the Environmental group. Note that the
current status of our two alarms can be monitored to the right.
Note: If the alarms were not configured to auto-acknowledge, you could acknowledge the
alarms by either right-clicking on them or one of the two buttons shown below:
5. Click on the History Search toolbar button.
Rev. 121908
Page 20
6. Set the Name mask to *.

7. Click on the Search link near the bottom of the History Search pane.
8. In the History Results pane, click on the Start Time column header to sort the results based
on start time.
9. Observe how you can see a list of the occurrences of both alarms including their durations.
Rev. 121908
Lesson 13
Configuring Event Framing - PIBaGen
What You Will Learn
How to configuring the PIBaGen To Populate Batches
This exercise covers creating a PIUNIT in the module database. It can be configured to work
with PIBaGen. The batch counter can be used as the batch active and batch label tag. The phase
counter will be used as a sub-batch id and label. The PIBaGen service may need to be manually
started.
Reference:
The PI Batch Generator Interface (PIBaGen) collects data from the Historian Server (from the
Historian Data Archive and the PI Module Database), generates batch data and writes the batch data to the
Historian Server in the Batch Database. PIBaGen is used when there is no native interface to generate
and store batch data in the PI System. PIBaGen automatically generates PIUnitBatches, Batches and Sub
Batches for each PIUnit that is configured and registered. The generated batch information can be
accessed using tools like BatchView and PI Batch Database Editor. This interface is not UniInt based and
does not support any Failover. It only populates the PI Batch Database based on PI Events and does
populates only one PI Point which represents the status of the interface.
A PIUnit represents a piece of equipment in which a product is processed in batches. The Aliases
of the PIUnit define the PI Points associated with the equipment. Each time a product is
processed through a PIUnit, a PIUnitBatch is created. Since there can be only one batch
processed in a piece of equipment at any time, there can be only one PIUnitBatch associated with
a PIUnit at any time
A PIUnitBatch is the data object that encapsulates one ISA S88 concept of a batch. Here is the
definition from S88: The material that is being produced or that has been produced by a single
execution of a batch process.
PIBaGen recognizes the start and end of the processing in a PIUnit, and therefore the start and end of the
PIUnitBatch, by changes in values of a PI Point known as Active Point. Starting a PIUnitBatch includes
writing the start time and other properties of PIUnitBatch like Batch ID, procedure name, product name
etc., to the PI Batch Database. PIBaGen optionally also adds the PIUnitBatch to the collection of
PIUnitBatches under an object called Batch.
A Batch is used to record the production of a specific Batch; in practice this usually involves one or
more PIUnitBatches in one or more PI Units (one or more pieces of equipment). A Batch allows
collecting related PIUnitBatches. All the Batches and properties associated with Batches, like Product
Name, Batch Recipe, etc., are stored in the PI Batch Database.
The SubBatch information is also written to the PI Batch Database by the PIBaGen interface. A SubBatch
is a definable portion of a PIUnitBatch and is always associated with a PIUnitBatch. The start and end
time for each of these definable portions is determined by a separate Active Point called SubBatch
Active Point. Examples of S88 Sub-batches are Operations and Phases. Every SubBatch has a name, a
Heading and a collection of Sub Batches associated with it. The SubBatch collection allows for a
hierarchy of Sub Batches.
Rev. 121908
Lesson 13 Configuring Event Framing - PIBaGen
Page 2
Specifying the PI Points for Active Points and all other properties of Batches, PIUnitBatches and Sub
Batches is called the PIUnit Configuration. PIUnit configuration is stored as Aliases and Properties in
the PI Module Database. The creation and configuration of the PIUnit is done using the PI Batch
Generator Plug-in for PI SMT.
Reference Manuals:
Batch Generator (PIBaGen) Interface to the PI System Guide

C:\Program Files\Rockwell Software\FactoryTalk
Historian\Server\PIPC\Interfaces\PIBaGen
Other Reference Manuals

1. PI Server Installation Guide for information on installation of the Batch Database and
PIBaGen
2. PI SDK User Manual and Help file, for information on PI Batch objects and
programmatically writing or editing batches and on the PI Module Database.
3. PI System Management Tools (PI SMT) online Help files, for information on using the PI
Batch Generator plug-in and Batch Database plug-in
4. Batch Database Support of the PI Batch Subsystem, for information how the PI Batch
Subsystem data can be supported through PI Batch Database and PI-SDK, the impact on
existing batch applications, and for techniques to move to the PI Batch Database.
5. PI BatchView User Manual, for information on viewing batches using the BatchView
software.
6. Batch and Event Framing for Process Analysis Course Materials
Rev. 121908
Page 3
Exercise:
image.
2. Launch the Interface Configuration Utility (ICU).
3. Click the Import Existing Interface from .BAT file toolbar button
4. Navigate to the PIBaGen subdirectory location: C:\Program Files\Rockwell

Software\FactoryTalk Historian\Server\PIPC\Interfaces\PIBaGen.
5. Open the file named PIBaGen.bat
6. The Interface will be named: PIBaGen
7. Change the type from none to other_non_uniint.
Rev. 121908
Page 4
8. From the ICU toolbar click Save.

9. Click Yes to continue when warned that no point source has been specified.
10. In the Service area, set Startup Type to Auto and click the Apply button.
11. Click the Start button on the toolbar
12. Open Windows Computer Manager Services and check that the newly created PIBaGen
service is running (click Start Administrative Tools Services and look for PI Batch
Generator Interface)
Rev. 121908
Page 5
13. Click the Close button to close the ICU.

14. Using windows explorer navigate to the directory C:\Program Files\Rockwell
Software\FactoryTalk Historian\Server\PI\adm
15. Right-click on pisrvsitestop.bat and select Edit from the context menu
16. Remove the REM statement from the net stop pibagen
17. Save and Close the file

18. Right-click on pisrvsitestart.bat and select Edit from the context menu
Rev. 121908
Page 6
19. Remove the REM statement from the net start pibagen

21. Right-click on pisitestart.bat and select Edit from the context menu
22. Remove the REM statements from the PI-Batch Generator block
Create a new PI-UNIT

2. Expand the Operation category and select the Module Database plug-in.
3. Expand VM-HIST-1 and right-click on Modules and select New.
Rev. 121908
Page 7
4. Name the Module Reactor Section and click OK. Then, right-click on Reactor
Section module and select New to create a new PIUnit.
Note: A PI-Unit can also be created from the SMT Batch Generator plug-in MDB View
(Module Database View)
5. Enter T100 into the Module Name field and click OK
6. Assign an alias to the PI-Unit, right-click on the T100 module and create a new Alias
Rev. 121908
Page 8
7. Enter Temperature into the Alias Name field and map it to the T100_Demo_Temp.PV tag,
and click OK.
8. Launch the FactoryTalk Administration Console.
9. Click Network directory, click OK.
10. In the FT Administrator console explorer, right-click InstaCorp, point to and click Add
Individual Historian Points
Rev. 121908
Page 9
11. Set the Using data collection interface to FTLD2.

12. Set the scan class for new point to 1 second.
13. Select Browse Tags.
14. Browse InstaSoap \ Mixing \ CLX1 \ Online and select the tags T100_Batch_Counter.ACC
15. Click Add Tags(s) to List, (the selected tag will be displayed in the lower window) and click
OK.
Rev. 121908
Page 10
16. Note: The tag have been added to the Selected tag(s) and have the syntax /Instasoap
/Mixing:[CLX1]T100
17. Click OK.
18. Note: The new tag just added to the FT Historian will have the name:
InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Batch_Counter.ACC
19. Switch back to System Management Tools (SMT).
Rev. 121908
Page 11
20. Expand the Batch category and select the Batch Generator plug-in:
21. Select VM-HIST-1 in the middle pane under Registered Units Only tab.
22. Select the Interface tab in the right pane.
23. Set the Configuration Module Name to PIBaGen
24. In the middle pane, click the Save toolbar button
Rev. 121908
Page 12
25. Switch to the MDB View tab and navigate to the T100 PIUnit (VM-HIST-1 -> Reactor
Section ->)
Rev. 121908
Page 13
26. Using Batch Generator plug-in, (the right hand configuration view), select the
PIUnitBatches tab and configure the following:
Set the Active Point to use the T100_Batch_Counter.ACC tag
ActivePoint Behavior to use Step and the Include zeroth state (Continuous) box is
checked
Set Unit Batch ID Point to use the T100_Batch_Counter.ACC tag
Change the Recovery Options checkbox to Do not recover anything.
27. Select the PISubBatches tab and right-click on the SubBatch Hierarchy. Right click to
Add New SubBatch or click the New SubBatch Configuration icon
Rev. 121908
Page 14
28. Name the SubBatch Heating

29. Using SubBatch configuration view, configure the following:
Set the Active Point to use the T100_Phase_Counter.ACC tag
ActivePoint Behavior to use Step and the Include zeroth state (Continuous) box is
checked
Set SubBatch Name Point to Use ActivePoint value
Rev. 121908
Page 15
30. In the Batch Generator plug-in tree view, select and right-click the T100 PIUNIT and Save
(or use the Save icon on the tool bar).
31. Right-click again on the T100 PIUNIT and select Register.
32. Expand the Batch Database plug-in.

33. Expand the tree until you can see the T100 unit in the center window
34. Select and right-click T100 to Search for PIUnitBatch, or click on the Search for
PIUnitBatch .
Rev. 121908
Page 16
35. Ensure that the PIUnitBatch search PIUnit field will be populated with \\VM-HIST\Reactor
Section\T100, if not, enter T100.
Note: if you starting the search from the top of the Batch database tree, then the PIUnit field
would contain an * then replace this with T100.
36. Click OK.
Rev. 121908
Page 17
37. Expand the Batch database search results and verify that Unit Batches are being created by
PIBaGen.
In the following example, there are 7 Unit Batches: the last unit batch in the list (1086) is still
running with PISubBatches 0 and 1, the previous unit batch (1085) started at 2/5/2008
2:53:00.733 PM and ended at 2/5/2008 2:54:15.92001 PM completing PISubBatches 0, 1, 2
and 3.
Rev. 121908
Page 18
Rev. 121908
Lesson 14
Using BatchView
What You Will Learn
To configure a BatchView Group in ProcessBook

To compare a sub-batch phase against a golden batch
In this exercise, you are going to be looking at a couple ways to visualize the batch information
being generated by the results of the previous exercise, (Exercise 12 - Event Framing
PIBaGen).
Configure a simple BatchView Group trend of the batches in absolute time view. Then switch to
a relative view and pick a batch to represent a golden batch. Align a phase of the golden batch
for comparison against other sub-batches
Rev. 121908
Lesson 14 Using BatchView
Page 2
Exercise:
image.
2. Build a basic ProcessBook display for our BatchView. Launch ProcessBook.
3. Click the New button on the toolbar.
4. Select the type as ProcessBook display (pdi) file and enter BatchView in the Display Name
field.
5. Click OK
Rev. 121908
Page 3
6. Verify you are in build mode, the build mode icon on the toolbar will be highlighted (if you
are not, in build mode, click the build mode icon to change to build mode).
7. Select the Batch Group button on the ProcessBook toolbar.
8. Drag a Batch Group into the empty space which covers most of the work area.
9. In the Search Parameters area, change the following:
Unit Name parameter from * to T100
Time Range and Duration to between: *-10m and *
Rev. 121908
Page 4
11. From the Available Aliases pane at the bottom of the Batch group definition dialog, select the
Temperature alias and click the Add Alias -> button.
Rev. 121908
Page 5
12. Select the Layout tab.

13. From the Visible Symbols pane, check the Results check box.
Rev. 121908
Page 6
14. Select the Settings tab and from the Plot Time pane, set the Absolute radio-button.
15. Click OK. The display may take a moment to retrieve all the data.
16. When the display appears, select the Run button on the ProcessBook toolbar.
Rev. 121908
Page 7
17. All the batches active during the last ten minutes are displayed in absolute time from the start
of the first batch to the end of the last batch.
18. Note: The most recently completed batch is coloured dark red, while the still in-process
batches are coloured light green.
19. Note: The temperature alias is in color to match the batch that it corresponds with.
20. In the Results Panel, select a Unit Batch and click the
21. In the Batch Gantt Panel select a Unit Batch

Sub-Batches.
symbol to show the Sub-Batches.
and click the
symbol to show the
Rev. 121908
22. To display precise time information of a unit batch, right-clicking on Unit Batch
from the context menu select Properties
Page 8
and
Rev. 121908
Page 9
23. Change back to build mode, select the Build button on the ProcessBook toolbar.
24. Double-click on the Batch Group chart.

25. Select the Settings tab.
26. From the Plot Time pane, set the Relative Start and End Time radio-button and click
OK.
Rev. 121908
Page 10
28. Note: The unit batches are aligned based on their start time. Times along the x-axis are now
seconds into the batch.
29. Pick a Unit Batch that you would like to be the Golden Batch.
30. Click in the Anchor column
symbol in the results pane for that Unit Batch.
31. The batch turns yellow to indicate it is the Golden Batch. The batch will be prevented from
expiring from the search results.
32. Select the Golden Batch, and then click the
symbol to show the Sub-Batches.
33. Suppose the 2nd phase of the unit batch is particularly critical for the process, you can align
all the unit batches based on their 2nd phase of the golden batch.
Rev. 121908
Page 11
34. Right-click on the 2nd phase of the golden batch and select Align to every PIUnitBatch\2
from the context-menu.
Rev. 121908
Page 12
35. Expand some of the sub batches and compare the 2nd phase against that of the golden batch.
This completes this exercise
Rev. 121908
Lesson 15
Working with Digital States
What You Will Learn
How to configure a digital state set and create a digital tag

which uses it, all with the System Management Tools.
Digital tags provide the ability to record information about discrete states, such as: running, idle,
e-stop, shutdown. Digital tags cannot be created without assigning them to a digital state set.
First you must use the System Management Tools to create a digital state set.
Rev. 121908
Lesson 15 Working with Digital States
Page 2
Exercise:
image:
3. Expand the Points category and select the Digital States plug-in:
4. In the Digital States plug-in, first select the VM-HIST-1 server at the top of the tree.
Once that is selected, you will be able to click the Add Digital State toolbar button:
Rev. 121908
Page 3
5. Type in a name of Machine_State:
6. To the right of the Digital State names, start by clicking in the State Name column. Enter
the text Manual:
7. Fill in all the following values (be sure to press Enter after typing in the last State Name of
Failed so the Failed state actually gets entered):
8. Click on the Save toolbar button so that your changes are not lost:
Rev. 121908
Page 4
9. Open the FactoryTalk Administration Console and right-click on the Mach3 Area of Line1
of the Application MyApp. Select Add Individual Historian Points
10. Select Browse Tags:
Rev. 121908
Page 5

Select the Program:MainProgram
Select StoreValue_3 tag
Click OK
12. Click OK on dialog that follows to add this tag to Historian.
Rev. 121908
Page 6
13. Now that you have created the Machine_State digital state set, we can create a new digital
point that uses the created digital state set. To begin, select the SMT Point Builder plug-in:
14. Click on the Search button:
Rev. 121908
Page 7

Enter Tag Mask of *Value_3*
Click Search
Select the StoreValue_3 tag
Click OK
Rev. 121908
Page 8
16. Click on the StoreValue_3 tag and on the General tab, create a new tag by setting the
following fields:
o Name:
Machine1_Current_Status (overwriting the StoreValue_3 tag
name)
o Point type:
Digital
o Digital set:
Machine_State
17. Click the Save button on the toolbar:
18. Do the following step:

Select the Data-Current Values tool in the SMT
Search for the Machine1_Current_Status and StoreValue_3 tags to display
Rev. 121908
Page 9
19. We now will manually change the value of the StoreValue_3 tag in the CLX processor to
simulate values that will trigger different States. Open the Data Client tool from Start ->
All Programs -> Rockwell Software -> FactoryTalk Tools:
20. If requested, select FactoryTalk and Network Connection:
Rev. 121908
Page 10
21. Select Mach3 of Line1 of the MyApp application and click OK:
22. Click OK on the following dialog:
Rev. 121908
Page 11
23. Select the StoreValue_3 tag in the Program:MainProgram location and click OK:
24. Right-click on the tag and select Async Write:
Rev. 121908
Page 12
25. Type in a value of 1 and then click OK. If you look at the SMT Current Values, you
should see the StoreValue_3 tag with a value of 1 and the Machine1_Current_Status of
Auto.
26. Experiment with changing the value of the StoreValue_3 tag from 0 to 4. All 5 states you
entered in the Machine_State Digital State Set should be able to be displayed.
Displaying with ProcessBook

Rev. 121908
Page 13
3. Select new ProcessBook Display (.pdi) File, set the Display Name to Test, and click
the OK button:
Rev. 121908
Page 14
7. Click on the Tag Search button to select the Machine1_Current_Status tag (refer to
previous lessons for detailed steps). Set the Plot Time Start to *-15 Minutes. Click the
OK button:
Rev. 121908
Page 15
8. Use the Trend Cursor to explore the data of the new tag:
Rev. 121908
Page 16
Rev. 121908
Lesson 16
Using FTLD Health Points
What You Will Learn
How to configuring FTLD Health Points
In this exercise, you will configure the FTLD interfaces health points. These points will give
you a view into how long various functions of the interface are taking.
Rev. 121908
Lesson 16 Using FTLD Health Points
Page 2
Exercise:
1. Verify that you are on the VM-DATA-1 image by checking the hostname on the background
image.
3. Select the FTLD2 interface from the drop-down box.

4. Select the Health Points sub-category under UniInt in the left pane.
Rev. 121908
Page 3
5. Right-click on one of the points and select Create All from the context-menu.
6. Acknowledge the error in creating the first point because of a licensing restriction, click
OK.
7. The status remaining health points (except the first point) should indicate Created.
8. Close the ICU.

Rev. 121908
Page 4
12. Enter a Tag Mask of sy* and then click the Search button.
13. Click the Select All button.
14. Click OK.
Rev. 121908
Page 5
15. Using the Current Values SMT plug-in, click on the Run toolbar button.
16. Observe the Current Values for a each FTLC Health point:
Note the IO Rate indicates the number of items sent to the server since the last
heartbeat
Note the output rate and output bad value rate which accumulate counts during the
performance period which defaults to 8 hours
Note that advise mode tags are shown in scan class 0 regardless of their actual scan
class
Note that polled / event and output mode tags are not shown in any scan class
Rev. 121908
Page 6
Rev. 121908
Lesson 17
Using and Displaying Audit Information
What You Will Learn
Use SMT to enable auditing of your PI Server

Use PI AuditViewer to examine the activity from this
week class
There are two methodologies to auditing the FactoryTalk Historian server:

PI Audit Trail Message Log
Reports changes only to snapshot, archive, and base subsystems
PI Audit Database Mechanism a newer and a more secure method for logging system
activities (preferred)
Reports changes to all subsystems.
This exercise is base on the PI Audit Database Mechanism
Reference: Historian Auditing User Guide C:\Program files\Rockwell Software\FactoryTalk
Historian\docs\Historian SE 2.0 Auditing User Guid.pdf
Rev. 121908
Lesson 17 Using and Displaying Audit Information
Page 2
Enable auditing of your PI Server

image.
3. Expand the Operations category and select the Tuning Parameters SMT plug-in.
Rev. 121908
Page 3
4. In the Tuning Parameters plug-in, first select the EnableAudit server at the top of the
tree. Once that is selected, you will be able to double-click to display the properties window.
Note: Auditing mask - the entered value is a bit mask where each bit refers to a specific
database -1 enable the audit of all databases. Masked parameter (Point:1, Digital Sets:2,
Attribute Sets:4, Point Class:16, User:32, Group:64, Trust:128, Module:256, Heading:512,
TransferRecord:1024, Campaign:2048, Batch:4096, UnitBatch:8192, Snapshot:268435456,
Archive:536870912, DBsecurity:1073741824)
5. Change the auditing Value to -1 and click OK
Rev. 121908
Page 4
6. For the auditing entered value to take effect FT Historian must be stopped and restarted
7. Click the Stop FT Historian System.bat icon if on the desktop, or select Start Programs
Rockwell Software FactoryTalk Historian Stop FT Historian system
8. Once all of the services have stopped, click the Start FT Historian System.bat icon if on
the desktop, or select Start Programs Rockwell Software FactoryTalk Historian Start
FT Historian system
Use PI AuditViewer to Examine the Activity

With auditing enabled the audit database mechanism reports changes to all subsystems, all data
added, edited or removed from the system including database configuration changes. In this
exercise, you are going to substitute a tag value and view the change in the FT Historian
AuditViewer.
1. Change or substitute a tag value, you will use the archive edit in SMT for this function.
2. Expand the Data category and select the Archive Editor plug-in.
Rev. 121908
Page 5
3. From the archive editor, you need to search / select the tag value we wish to view / modify.
In this case I have selected the tag T100_Demo_Temp_DegC (you may choose a different
tag). The archive editor will display data for the time period specified in the low window.
4. From the archive editor select the value you want to change and enter a new value (modified
value of 99 in this example), tab all the way across the columns, then click the save icon
followed by Get Events
. The modified value will be displayed and marked as substituted.
Rev. 121908
Page 6
5. From the SMT Tools menu select AuditViewer and launch the application.
6. From the AuditViewer expand the Manage section and click the Manage link
7. Double-click the Archive 0 icon to display the subsystems files details.
Rev. 121908
Page 7
8. From the subsystem details page scan each of the files in turn by selecting the Scan File
button from each of the three subsystem views.
9. Confirm that the record is updated.
10. You can also view this in table form. From the menu bar select the Table tab.
Rev. 121908
Page 8
11. Change the search Start Time to reflect the time period when the change was made, (in
this example, the past 5 minutes).
12. Select Search to display and audit records for the time period specified.
Note: FT Historian Audit Records are presented in a hierarchical grid format in the Results
pane.
13. To view more detailed information, select the entry you wish to view and click the + symbol,
this will display detailed information about the tag value old and new value, if marked
substituted etc.
Rev. 121908
Page 9
14. Detail Information can also be accessed by clicking on the "Details" options from the right
mouse-click menu.
15. Change the start time to say 1 month and the end time to now (*) and then select search to
display the audit files for the last month, (If Start Time and End Time are both left blank,
then all AuditRecords will be returned.
16. From the File menu select the Export option and save the export file in csv format.
Rev. 121908
Page 10
17. Select the export file just saved and open, review the contents of the exported audit file. Can
you find the changes you recently made?
18. Self directed task - try changing other tag values and using the filter options and custom
setting found in the left-hand window.
Select the required filter criteria in the Filter tab.

Click on the Apply button to apply the filter criteria to the Search results set
Click Search if a new Time Range and Filter criteria are to be applied
Sort Data by clicking on the Column Headers
Optional Exercise
How to create a new empty file
The subsystem auditing must be set offline to copy, delete, export, move, or back up Audit
Database files. In addition, you can perform administrative activities on Audit Database files
when the corresponding subsystem is stopped.
To place subsystem auditing offline, use the command:
piartool systembackup start subsystem <subsystem>
Note: As of version 2.00, the PI Server supports online backups as described in the
PI Server System Management Guide. To maintain backward compatibility, the
Rev. 121908
Page 11
command piartool systembackup is still used to control subsystem auditing.

Piartool.exe is located at C:\Program Files\Rockwell Software\FactoryTalk
Historian\Server\PI\adm
The audit file at located at C:\Program Files\Rockwell Software\FactoryTalk
Historian\Server\PI\log
1. Open a command window

2. Change to directory C:\Program Files\Rockwell Software\FactoryTalk
Historian\Server\PI\adm
3. Place the archive subsystem (piarchss) into backup mode with:
piartool -systembackup start -subsystem piarchss
Note: Audited subsystems can remain in auditing offline mode for limited periods, after which
they
Automatically switch to auditing online mode:
The PI Snapshot subsystem, because of critical data-loss prevention duties, switches to
auditing online mode after 5 minutes.
The PI Archive subsystem and PI Base subsystem switch to auditing online mode after 30
minutes.
4. Copy the data file from the log directory to another location (either through windows
explorer or the command line).
5. Delete the file from the PI System log directory, (either through windows explorer or the
command line).
Rev. 121908
Page 12
6. Place the archive subsystem (piarchss) system back to online mode with:
piartool -systembackup end -subsystem piarchss
Note: When a subsystem enters auditing online mode, it creates a new data file. If file creation
fails, the piartool backup command will return an error and the subsystem automatically reenters auditing offline mode. If the problem persists, the aautomatically switch to auditing online
mode cycle continues until the audit file is successfully opened. In addition, this activity is
written to the Message Log.
7. The above replacing / creating the audit database files can be carried out for each of the three
subsystems:
The following commands for each subsystem can be run from the PI\adm directory:
PI Archive
piartool systembackup start subsystem piarchss
copy ..\log\piarchssaudit.dat ..\pi\temp
del ..\log\piarchssaudit.dat
piartool systembackup end subsystem piarchss
PI Base
piartool systembackup start subsystem pibasess
copy ..\log\pibasessAudit.dat ..\temp
del ..\log\pibasessAudit.dat
piartool systembackup end subsystem pibasess
PI Snapshot
piartool systembackup start subsystem pisnapss
copy ..\log\pisnapssAudit.dat ..\temp
del ..\log\pisnapssAudit.dat
piartool systembackup end subsystem pisnapss
Rev. 121908
Lesson 18
Using Archive Management Tools
What You Will Learn
How to create various sized archive files and how to register

and unregister archives.
Managing archives in FactoryTalk Historian is a straight-forward task. You can use the
Archives plug-in. for SMT to create, register, and unregister most archives. If you want to create
new archives smaller than your primary archive, you need to use the pi command line utilities
which can sometimes be helpful in testing environments.
Three Archive files are created at default. Each 128 MB in size.
Rev. 121908
Lesson 18 Using Archive Management Tools
Page 2
An Archive Shift occurs automatically when an archive file becomes approximately 99% full.
When an Archive Shift occurs, either a new archive file will be created or an existing file will
be used. This is controlled by a Tuning Parameter called Archive_AutoArchiveFileRoot.
Rev. 121908
Page 3
If there is a valid path specified in the Archive_AutoArchiveFileRoot parameter (path must

exist), a new archive file will be created when an archive shift occurs.
If the Value (path) in this parameter is empty or blank, when a file shift occurs an existing file
will be used. The archive file must already exist and be registered in the FactoryTalk Historian
Server. The selection of the specific file that will be used is:
If more than one empty archive files exists, the most recently created archive file will be
used.
If there are no empty archive files, the oldest full file will be used. The archived data
already in this file will be erased and new archive data be written to it.
Rev. 121908
Page 4
Exercise:
image:
2. Launch the System Management Tools (SMT):
3. Expand the Operation category and select the Archives plug-in:
4. Click the Create a new archive toolbar button:
Rev. 121908
Page 5
5. Leave the default Archive path and Archive name. Switch to the option to Create
archive larger than current primary. Set the size to 192 MB and then click the OK
button:
6. Recall that we could create a fixed time archive, or an archive of the same size or larger than
the primary archive. To create a smaller archive we need to use the pi command line tools.
Leaving the SMT running in the background, launch a Command Prompt:
7. Change to the directory:

C:\
C:\Program Files\
Files\Rockwell Software\
Software\FactoryTalk Historian\
Historian\Server\
Server\PI\
PI\adm
8. To create an archive only 50MB in size, which is smaller than the primary, run the command:
piarcreate ..\
..\dat\
dat\piarch.005 50
Rev. 121908
Page 6
9. We could register our new archive with the SMT, but since we are here, lets use the pi
command line tool. Run the command:
piartool ar ..\
..\dat\
dat\piarch.005
10. Leave the Command Prompt running and switch back to the SMT. Click the Refresh
toolbar button so the new archive file is displayed:
11. Typically when you have quite old archive files, you will want to move them off to a readonly medium or network accessible storage. The archives can still be queried by simply
registering the new location with FactoryTalk Historian. Click on our newly created
piarch.005 archive and click the Unregister selected archive" toolbar button:
12. Click Yes on the confirmation dialog:
Rev. 121908
Page 7
13. Leave the SMT running and switch back to your open Command Prompt. Run the
command:
mkdir c:\archives
14. Now run the command:

move ..\dat\piarch.005 c:\archives
15. Close the Command Prompt and return to the SMT. Click on the Register an archive
toolbar button:
16. Navigate to the directory C:\archives, select the file piarch.005, and click the Open
button:
Rev. 121908
Page 8
17. Verify that piarch.005 shows up in the archive list:
18. Close the SMT, this exercise has been completed
Rev. 121908
Lesson 19
Scheduling Backups of Historian Data
What You Will Learn
How to schedule a daily backup of FactoryTalk Historian.
Its important to back up the FactoryTalk Historian Server at least once a day, so that you don't
lose data and configuration information if something goes wrong with your equipment. All
backups of Historian that are done while the Historian System is running are managed by the PI
Backup Subsystem.
Rev. 121908
Lesson 19 Scheduling Backups of Historian Data
Page 2
Part A: Create a Scheduled Task to Perform Backups

image:
2. Open a Command Prompt by selecting Start Command Prompt:
3. In the command prompt, change directories to the location:

C:\Program Files\Rockwell Software\FactoryTalk Historian\Server\PI\adm
Rev. 121908
Page 3
4. Type pibackup and press Enter. You should get the following. Please read through the
information, including descriptions of the backup path, number of archives, archive
cutoff date and -install parameters:
5. To create a Scheduled Task that will backup Historian in C:\Backup, including the 5 most
recent archives, enter the command:
pibackup C:\Backup 5 install

6. Examine the end of the text output and verify that the script completed successfully:
Rev. 121908
Page 4
7. Close the Command Prompt and launch the Services applet from the
Administrative Tools program group:
8. Verify that the Task Scheduler service has a Status of Started:
Rev. 121908
Page 5
9. Close the Services window and open the Scheduled Tasks folder by doubleclicking on the Scheduled Tasks entry on the Control Panel menu:
10. Verify that the PI Server Backup task has been created and has a Next Run
Time of 3:15 AM on tomorrows date (the day after the date that you created this task).
Note that 3:15 AM is the default for this task controlled by settings within the pibackup.bat
file:
Rev. 121908
Page 6
11. Since we dont want to wait until 3:15 AM tomorrow morning, right-click on the task and
select Properties:
12. On the Schedule tab, enter a start time of two minutes past your computers current time
(2:25 PM in below example). Click Apply and OK:
Rev. 121908
Page 7
13. Wait for the task to automatically run and complete:
14. On the C: drive you should now have a Backup folder with contents such as the below.
The subfolders store the backup configuration files and archives. The .txt file is a log file
that stores information about the backup that you have just completed:
Note: The pibackup will create incremental backups to these files every day, except for
Mondays when full backups are again performed. These settings are within the pibackup.bat
file and could be edited. If you want to force a full backup, deleting the contents of this
Backup folder and then re-running the backup will once again create a full backup.
Rev. 121908
Page 8
15. Open and look through the backup log file. Check at the end that the backup script
completed successfully:
16. Note the WARNING!! WARNING!! WARNING!!...in this log file about no
pisitebackup.bat file. The pibackup.bat file is only backing up to your local hard drive. You
should also back up to a separate computer in order to recover from a hard disk crash of the
computer running Historian Server.
Rev. 121908
Page 9
Part B: Creating a pisitebackup.bat file to Backup to Remote Computer

1. Open Windows Explorer, navigate to the directory specified below and find a file by the name of
pisitebackup.bat.example:
2. Right-click on this folder and select Properties and change to non-read only (un-select
checkbox):
3. After clicking OK on Properties dialog box, right click on pistiebackup.bat.example file

and rename to pisitebackup.bat (delete the .example portion).
Rev. 121908
Page 10
4. Now, right-click on the pisitebackup.bat file and select Edit. Notepad should open and you
should be seeing the contents of this file. Following is an excerpt from this file. Edit the
areas shown below in bold, larger letters so that your version matches. You will be
identifying the VM-DATA-1 computer as the computer to send a backup to and also adding
quotation marks around %AdmPath% to fix a current issue with this .bat file.
::::::::::::::::::: EDIT THIS SECTION ::::::::::::::::::::::::::::
:: Change "remote_computer_name" to a valid remote computer name
set UNC_BACKUP_PATH_ROOT=\\VM-DATA-1\c$\pibackup
:: COPY SITE-SPECIFIC FILES HERE
:: EXAMPLE:
@REM if not exist "%BackupPath%\sitebackup" mkdir "%BackupPath%\sitebackup"
@REM copy /Y "D:\Program Files\PIPC\dat\pipc.log" %BackupPath%\sitebackup
:: If you are using a 3rd-party backup application to backup
:: application to backup your intermediate-backup directory, then
:: uncommnet the following line to prevent the interemediate
:: backup directory from being backed up by this script.
@REM exit /B %_siteretval%
:::::::::::::::: DO NOT EDIT BELOW THIS LINE :::::::::::::::::::::
::Cleanup from previous backup
erase /F /Q temp_sitebck_*
::Determine the time of the last backup
"%AdmPath%"\piartool -backup -query -verbose >
temp_sitebck_verbosequery.out
find "Last Backup Start:" temp_sitebck_verbosequery.out >
temp_sitebck_lastbackupstart.out
FOR /F "tokens=4-7 skip=2 delims=: " %%i IN (temp_sitebck_lastbackupstart.out)
DO SET PIBackupTime=%%i_%%j.%%k.%%l
5. Save your edits and close Notepad.
Rev. 121908
Page 11
6. Open the Properties of the Scheduled Task again:
7. So that this task has permission to write data to the VM-DATA-1 computer, specify the
user of Administrator and set password to rockwell. Click OK after making these
selections:
Rev. 121908
Page 12
8. Re-Run the pibackup by either changing the run time to a couple of minutes after your
computers current time (as you did in the last section of this exercise), or by right-clicking
on the Scheduled Task and selecting Run:
9. If you look on the VM-DATA-1 computer, there should be a C:\pibackup folder with
incremental backup information. A full backup will be performed by the scheduled task on
Mondays, unless the contents of the VM-HIST-1 computers C:\Backup folder is deleted in
which case a full backup will be performed if the Scheduled Task runs again.
Rev. 121908
Lesson 20
Configuring Interface Redundancy
What You Will Learn
How to configure FactoryTalk Historian LiveData interface

redundancy.
In the VMWare images being used in this class, RSLinx Enterprise is on the VM-CLX image.
We have been using VM-DATA-1 as an image to collect data via the FTLD2 interface. Another
VMWare image called VM-DATA-2 will now be used as a redundant interface to the interface
on VM-DATA-1. Up to this point in the class we have not powered on VM-DATA-2 in an
effort to reduce system load on our host operating system. In this exercise we are going to
configure a FactoryTalk LiveData interface instance on the second interface node which will
cooperate with the existing interface to provide interface level redundancy.
Rev. 121908
Lesson 20 Configuring Interface Redundancy
Page 2
Exercise:
1. Begin the exercise by powering on the VM-DATA-2 image.
2. Log in to the VM-DATA-2 image.
3. On the VM-DATA-2 image, we want to adjust the default connection timeout setting and
connect to the VM-HIST-1 server. Launch the AboutPI-SDK utility:
Rev. 121908
Page 3
5. Similar to how you did in the Add Historian Server Connection on Distributed Interface
Node section of Exercise 1, add the VM-HIST-1 server, remove VM-DATA-2 as a server
and change the Connection Timeout to 30 seconds. Click the VM-HIST-1 box to
verify connection. The dialog box should now resemble the below. Note that we are using
30 seconds for the purposes of this training. In the real-world you may need a time less or
more than 30 seconds. When finished, click the Close button and close the About PISDK.
7. Click the Import existing interface .BAT file toolbar button:
Rev. 121908
Page 4
8. Navigate to the LDInterface directory and select the FTLDInt_FTLD.bat.bak file. Click
the Open button.
9. You will be prompted to select the Host PI Server. Select VM-HIST-1 from the drop-down
box and click the OK button:
Rev. 121908
Page 5
10. Change the Interface ID from the default value of 1 to the same ID as that of our primary
interface on VM-DATA-1, Interface ID of 2.
11. Select the Service category in the left pane. Change the service ID to match the interface ID
of 2. Click the Save changes to the Service ID button next to the Service ID. Click Yes
to the service ID change confirmation dialog. Click Yes to save the interface before
changing the service ID and reloading:
Rev. 121908
Page 6
12. When the save and reload completes, return to the Service category. Change the Display
name to FTLD2 and then click the service Create button:
13. Select the Buffering command from the Tools menu:
14. Change the radio button to Enable buffering with PI Buffer Subsystem and click Yes on
the subsequent confirmation dialog:
Rev. 121908
Page 7
15. Select the Buffered Servers category and then select the VM-HIST-1 server from the dropdown box. Click the OK button to return to the main ICU window. Click Yes on the
confirmation dialog:
16. Select the General category and then go back to the Service category. When you do, click
Yes to confirm that you want the ICU to add the buffer subsystem dependency:
1. Switch to the VM-DATA-1 image:
Rev. 121908
Page 8
3. Select the FTLD2 interface from the drop-down box.

4. Select the Failover sub-category under UniInt in the left pane.
5. Check the box to Enable UniInt Failover.
6. Click the Browse button.
7. Select the FTLDInt2 located on VM-DATA-2 and then click on the OK button:
Rev. 121908
Page 9
8. Right-click on one of the failover tags and select Create UFO_State Digital Set on Server
VM-HIST-1 on the context-menu. Click OK on the success dialog.
9. Again right-click on one of the failover tags, but this time select Export Point
Configuration (.csv) on the context menu:
Rev. 121908
Page 10
10. Navigate to the HostRoot\Temp folder of the Z: drive (ask Instructor if there is an
alternative). This corresponds to the temp subdirectory of the host system. Click the Save
button.
11. Leave the ICU open and log in to the VM-CLX image:
12. Launch RSLogix 5000:
13. From the File menu, click Open.
Rev. 121908
Page 11
14. Select the FTHDemo.ACD file in the C:\RSLogix 5000\Projects folder (or folder identified
by Instructor) to open the project.
15. Verify that the following tags exist in your project in the Controller FTHDemo folder,
Controller Tags area. If so, skip to step 28. If not, follow steps 16-27 to create these tags
and download the revised project to the CLX processor.
FTLD_Active
DINT
FTLD_HB1
DINT
FTLD_HB2
DINT
16. In the controller organizer view, expand the Controller FTHDemo folder.
17. Right-click Controller Tags, point to and click New Tag
Rev. 121908
Page 12
18. Enter FTLD_Active into the Name field.

19. Select from the Data Type drop-down list the DINT data type.
20. Verify the following options in the image below, click OK.
21. Repeat steps 16 through 19 and create the remaining two tags, remember to select the correct
Data Type for each.
22. In the controller organizer view, double-click the Controller Tags icon to display the
controller scope tag monitor view.
23. Review the three new tags that you have created, double-click the control tags icon to display
the controller scope tag monitor view.
Rev. 121908
Page 13

25. From the Communications menu, click Download:
26. A download warning will be displayed, click Download:
27. When download is complete, set the controller back to Remote Run:
Rev. 121908
Page 14
28. Close RSLogix 5000 and switch to the VM-HIST-1 image:
29. Launch Excel.
30. Open the previously saved FTLDInt2_UniIntFailoverTags.csv located in the

HostRoot\Temp directory of the Z: drive (or location identified by Instructor). Or, as an
alternative, open the FTLDInt2_UniIntFailoverTags.csv file if provided in the Class
Files folder (ask your Instructor if unsure):
Rev. 121908
Page 15
31. Set the following tag attributes for the first six tags (may be done already if file provided in
Class Files folder was used):
Tag
FTLDInt2_UFO_Active_IN
Instrumenttag
InstaCorp/InstaSoap/Mixing:RSLinx
Enterprise:[CLX1]FTLD_Active
FTLDInt2_UFO_Active_OUT
Enterprise:[CLX1]FTLD_Active
FTLDInt2_UFO_Heartbeat1_IN
Enterprise:[CLX1]FTLD_HB1
FTLDInt2_UFO_Heartbeat1_OUT InstaCorp/InstaSoap/Mixing:RSLinx
FTLDInt2_UFO_Heartbeat2_IN
FTLDInt2_UFO_Heartbeat2_OUT InstaCorp/InstaSoap/Mixing:RSLinx
location3 location4
1
1
2
32. To create the new tags, select the Export Tags command on the PI-SMT menu.
33. In the Export PI Tags dialog, verify that the Mode is set to Create and click the OK
button.
Rev. 121908
Page 16
34. Click OK on the results dialog:
35. Close Excel and switch back to the VM-DATA-1 image:
36. Click the Restart interface service toolbar button and click Yes when asked if you want
to save the interface configuration:
38. Click the Start interface service toolbar button:
39. Switch over to the VM-HIST-1 image:
Rev. 121908
Page 17
42. Add all of the FTLDInt2_* tags to the current values monitor and click the Start Updating
toolbar button:
43. Leaving the SMT open, launch ProcessBook:
Rev. 121908
Page 18
44. Create a new ProcessBook Display (.pdi) and draw a Trend on it. Add the T100_Sim_Vol
tag and configure the time range for the last 5 minutes:
45. Switch back to the VM-DATA-1 image:
Rev. 121908
Page 19
47. Right-click on Local Area Connection and click Disable:
48. Switch back to the VM-HIST-1 image:
49. Can you see where the network was disconnected? Does data collection continue even
though the network was disconnected?
Rev. 121908
Page 20
51. Right-click on Local Area Connection and click Enable:
53. Watch the SMT current value until the Interface_1_State changes to Backup. If the state
also says No PI, continue waiting.
Rev. 121908
Page 21
56. Right- click on Local Area Connection and click Disable:
58. Can you see where the network was disconnected? Does data collection continue even
though the network was disconnected?
Rev. 121908
Page 22
60. Right- click on Local Area Connection and click Enable:
62. Watch the SMT current value until the Interface_2_State changes to Backup. If the state
also says No PI, continue waiting.
63. Try writing a value (1 or 2) to the FTLD_Active tag in the CLX processor (via RSLogix
5000) to manually force an interface changeover even though both nodes are connected.
64. When you are finished experimenting, revert back to non-redundant conditions by:
a. Make sure Interface_1_State (VM-DATA-1 image)is Primary
b. Use ICU on VM-DATA-1 image to de-select Enable UniInt Failover and
accept/save changes
c. On the VM-DATA-2 image, shutdown the image by selecting Start Shut Down,
enter some comment and click OK
Rev. 121908
Lesson 21
Using View SE Updated Trend Object to Display
Historian Data
What You Will Learn
How to use the updated trend object for FactoryTalk View to

display data from FactoryTalk Historian.
FactoryTalk Historian provides an updated FactoryTalk View SE trend object. Installation of

this updated object will allow you to add pens to the trend which take their data from the
FactoryTalk Historian archive in addition to the traditional Live Data and Data Log Model
sources.
Rev. 121908
Lesson 21 Using View SE Updated Trend Object to Display Historian Data
Page 2
Exercise:
1. Verify that you are on the VM-DATA-1 image by checking for the following in the upper-left
corner:
2. Launch FactoryTalk View Studio:
Rev. 121908
Page 3
3. When prompted, select the Site Edition (Network) application type and click
Continue:
4. Open the InstaCorp application:
Rev. 121908
Page 4
5. Open the graphic titled process overview by double-clicking on it (in the MixingHMI
Graphics folder):
6. Use the Trend object to draw a box in some empty space:
Rev. 121908
Page 5
7. Double-click on the Trend object to get the configuration dialog:
8. On the General tab, change the Data Server to Poll historical data:
Rev. 121908
Page 6
9. On the Pens tab, change the Pen Source to Historian Server and then click
the Add Pen(s) button. Please note that the Pen Source selection only controls
the action that will be taken when the Add Pen(s) button is clicked. It does not have
any effect on existing pens, and should it switch back to the default value after a pen is added
this does not indicate that the pen is no longer using the Historian Server source.
Rev. 121908
Page 7
10. On the Add Pen Configuration dialog, click the button to launch the tag search
dialog:
11. On the Tag Search dialog Basic Search tab, change the Tag Mask to
*T100_Demo* and then click the Search button:
Rev. 121908
Page 8
12. Use Ctrl-clicks to select both the Temp.PV and Volume.PV tags. Click the OK
button:
13. Click on the Add button:
Rev. 121908
Page 9
14. Click on the OK button:
15. Change the Width on both pens to 3.
Rev. 121908
Page 10
16. On the Display tab, change the Maximum pen caption length to 80:
17. On the X-Axis tab, change the Time span to 5 Minute(s). Click the OK
button to finish:
Rev. 121908
Page 11
18. Verify that the pens have been added to the trend, then click the test (play) button:
Rev. 121908
Page 12
19. Experiment with and explore the trend. Note that the data is coming from the FactoryTalk
Historian archive and is not being updated from the snapshot table. This means that updates
will only be displayed when events pass the compression test.
This exercise is complete.
Rev. 121908
Lesson 22
Creating and Editing ProcessBook Trends
What You Will Learn
How to build basic trends in FactoryTalk ProcessBook and

use the multi-trend layout options.
Rev. 121908
Lesson 22 Creating and Editing ProcessBook Trends
Page 2
Part A Single-page ProcessBook:

image:
3. When you start ProcessBook, you will be prompted with an error connecting to node 49864.
The read-only PBDEMO.PIW starts every time you run ProcessBook and it is pointing to a
nonexistent Historian server. Click OK to point to the current Historian server. You will
have to do this every time you launch ProcessBook unless you go to some trouble to remove
the read-only property and save the remapped file.
Rev. 121908
Page 3
20. Close the ProcessBook demo file that opened at default and dont save when prompted:
22. Select the ProcessBook (.piw) File type. Give your new ProcessBook workbook
the name of Trends and click OK:
Rev. 121908
Page 4
23. Again, click on the New toolbar button:
24. Select the ProcessBook Entry type and then click the OK button:
25. Set the entry Label to Basic Trends and select an entry Type of Text. Click
the OK button:
Rev. 121908
Page 5
28. Set the entry Label to Simple Trend and select an entry Type of Display.
Set the Level to 2 and click the OK button:
Rev. 121908
Page 6
29. You should now have a ProcessBook workbook that looks similar to the following:
Rev. 121908
Page 7
33. On the General tab, click the Tag Search button:
34. Set the Point Source to ftld and click the Search button:
Rev. 121908
Page 8
35. Select the TI100 tag and click the OK button:
36. Set the Start time to *-5 Minutes and then click the OK button:
Rev. 121908
Page 9
37. You should now have a simple interactive trend:
Multi-Trend Layout
Now that you have some experience building a basic trend, we will use these skills to create
multiple trends arranged together.
Rev. 121908
Page 10
3. Set the entry Label to Multi-Trends and select an entry Type of Display.
Set the Level to 2 and click the OK button:
Rev. 121908
Page 11
7. Set the Plot name to Level. Use the Tag Search button to select the tag
T100_Sim_Vol [refer to previous section for detailed steps]. Set Plot Time Start to
*-5 Minutes. Do NOT click the OK button. Last, click the New Plot button:
Rev. 121908
Page 12
8. Set the Plot name to Temp. Use the Tag Search button to select the tag
TI100 [refer to previous section for detailed steps]. Set Plot Time Start to *-3
Minutes. Do NOT click the OK button. Last, click the New Plot button:
Rev. 121908
Page 13
9. Set the Plot name to T100. Use the Tag Search button to select both tags
T100_Demo_Temp.PV and T100_Demo_Volume.PV [refer to previous section
for detailed steps]. Set Plot Time Start to *-50 Seconds. Do NOT click the OK button.
Rev. 121908
Page 14
10. On the Display Format tab, select Plot-0 from the drop-down and DEselect the
Vertical Scale Inside Axis option. Do NOT click the OK button:
Rev. 121908
Page 15
11. On the Layout tab, fill in the following values:

o Row:
1
o Col:
2
o ExRow: 1
o ExCol: 1
These settings will cause the first (bottom) row to contain two columns (trends) and the
additional second row to contain one column (trend).
It is now safe to click the OK button. The only time you can access the Layout tab is
during the initial creation of a new trend. Once the trend is completed, you cannot go back
and edit the layout. The end result will be three separate trends which can be edited
individually.
Rev. 121908
Page 16
12. You should now have a lovely multi-trend:
13. Click on the Save toolbar button:
14. Save the processbook as Trends.PIW:
15. Close the Trends.PIW processbook file.
Rev. 121908
Page 17
Part B Multi-page ProcessBook

1. Create a new ProcessBook file and give it the name of Production Data:
2. With the Production Data ProcessBook open, select Tools Preferences:
Rev. 121908
Page 18
3. On the Start tab, uncheck the Run Mode Bias option (if not already unchecked). This
will keep the processbook from going into Run mode as items are added. Click OK
when finished:
4. Your processbook may have entered Run mode if your Run Mode Bias option was on
prior to step 3 above. Put the processbook in Build mode by clicking on the build icon in
the tool bar.
Rev. 121908
Page 19
5. In the last section, you always used the New button to add entries to the processbook. This
time, select the Insert menu and then Text:
6. Enter Label of Tank Levels and click OK
7. Again, select Insert Text and this time enter a Label of Tank Temperatures.
Rev. 121908
Page 20
8. One more time, select Insert Text and enter a Label of Miscellaneous. When finished,
your processbook should appear as follows. Note the three tabs creating individual pages
of your processbook:
9. Click on the Tank Levels tab to bring that page forward:
Rev. 121908
Page 21
10. Select Insert-Display:
10. Enter a Label of Tank 1 and change the Level to 3 which will result in indenting the
display name on the page a couple of times. Then, click OK:
Rev. 121908
Page 22
11. A blank processbook display will appear:
12. As you did in Part A of this exercise, add a Trend to this display using ControlLogix tag that
ends in T100_Sim_Vol. Your display should appear similar to the following (may need
to widen your trend for the tag name to appear on the right side such as in the below
example):
Rev. 121908
Page 23
13. Close the Tank 1 display. It will ask you if you want to save changes, be sure to click Yes:
You will actually be saving your entire processbook .PIW file (the display is embedded in it).
Save to My Documents:
14. Your processbook should now appear as follows, with a Display named Tank 1 under the
Text of Tank Levels:
Rev. 121908
Page 24
15. Select Insert Display again and name the new display Tank 2. Do not bother putting a
trend or anything else on the display for now. Close and save it. Your processbook may
appear as follows, with Tank 2 above Tank 1:
16. Obviously, if that is what you intended and prefer, no need to change anything. However, if
you want to change the order you could select View Outline. Instead of Book mode,
your processbook would then appear as follows:
17. If your processbook appears in this way, with Tank 2 above Tank 1, first select Tank1
and then click the arrow up button. The order should be changed.
Rev. 121908
Page 25
18. If you go back to View Book mode, your processbook should appear as follows (you
may need to click the Tank Levels tab to bring that page forward):
19. You may have noticed that the tabs on the right-hand side of the processbook are appearing
in reverse order of how we entered them, with Miscellaneous on top and Tank Levels on
the bottom. To reverse that order, go back to View Outline mode. Select the individual
lines of text that you added and use the arrow up and arrow down buttons to move the
order to match the following:
Rev. 121908
Page 26
20. When you go back to View Book mode, the tabs will now be in the order youve
specified:
21. Click on the Miscellaneous tab and select Insert Link / OS Command. Configure the
dialog box as follows. Use the Browse button to select notepad.exe from the directory
C:\Windows\System32 (will need to look for all files, not just .piw or .pdi files)
22. When your processbook is in Run mode, you now have a link to open Notepad in case you
wanted to enter some notes and save them, or open previously written notes that were saved
as .txt files in case you want to read them (try it!).
Rev. 121908
Page 27
23. Add another link on your Miscellaneous processbook page to launch Microsoft Excel. The
path to Excel on your computer should be C:\Program Files\Microsoft
Office\OFFICE11\EXCEL.EXE.
Note: As a possible enhancement, when Excel opens you could have it automatically open a
particular workbook if your link is configured similar to the following (this example assumes
C:\Production Report.xls actually exists and is a valid Excel workbook):
"C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE" "C:\Production
Report.xls"
24. As time allows, experiment with your processbook file adding items such as:
Add one or more displays to the Tank Temperatures page
Additional lines of Text as headings or section dividers on the pages
Change order tabs are displayed and/or order of items on pages
Launch additional applications from your processbook, such as the Windows
Calculator, Paint, etc.
Rev. 121908
Page 28
Rev. 121908
Lesson 23
Using Dynamic Elements in ProcessBook
What You Will Learn
How to use dynamic elements in ProcessBook displays to

create sophisticated displays.
Besides simple trends, you can also use dynamically updating elements in ProcessBook displays.
These are live elements whose properties change with time. This exercise will give you the
opportunity to work with the following:
Dynamic Text Value
Dynamic Bar Graph
Multi-State Symbol
Rev. 121908
Lesson 23 Using Dynamic Elements in ProcessBook
Page 2
PART A Edit Zero and Span of Tag with the SMT

In this exercise you will be using the tag T100_Sim_Volin the ControlLogix processor to
control some dynamic elements in ProcessBook. The value of this tag in the controller is
ranging between 0 and 120. In the Historian Point that is associated with this tag, it is important
to verify that the Zero and Span setting for this Point are correct.
image:
2. Open the System Management Tools (SMT):
Rev. 121908
Page 3
3. Select the VM-HIST-1 Server if not already selected, then open the Points options and
select Point Builder:
4. Select the Search icon:
Rev. 121908
Page 4
5. Set Tag Mask to *Sim_Vol*, click Search, select the T100_Sim_Vol tag and then
click OK:
Rev. 121908
Page 5
6. Select the Archive Tab and verify Zero is set to 0 and Span to 120. If not, make required
changes:
7. Click Save:
8. Close System Management Tools
Rev. 121908
Page 6
PART B ProcessBook Dynamic Elements

We are going to modify an existing ProcessBook display which contains a tank diagram. First
we will add a dynamic value to show the exact tank level. Then we will add two multi-state
symbols to act as high and low level alarm lights. Finally, we will use a dynamic bar graph to
visually display the level on top of the tank.
image:
3. Click OK to select the VM-HIST-1 Server (the demo that opens at default is expecting to
see a different server):
Rev. 121908
Page 7
5. Use the Open icon on the toolbar to open the file Ex04 PB Dyn Elem.PDI
located in the class files folder:
6. Because nothing is selected yet, we can set the default color properties for everything drawn
in the future. Click on the Drawing Color toolbar button (if grayed out, click somewhere
blank on the display to give it focus first):
7. Set the default Line color to black and then click the OK button:
8. If in Run mode, switch to build-mode and activate the Value toolbar button:
Rev. 121908
Page 8
9. Click on the background to the right of the tank to initiate the dynamic value dialog:
10. Click on the Tag Search button:
Rev. 121908
Page 9
11. Change the Tag Mask to *Sim_Vol* and click the Search button. Select the
T100_Sim_Vol tag and then click on the OK button:
12. Click on the OK button:
Rev. 121908
Page 10
13. Now select the static Text toolbar button:
14. Click just above the dynamic level value and type the text Level:
15. Now select the Ellipse toolbar button:
16. With the Ellipse tool, use click-and-drag to draw two small circles next to the tank.
You can force a circle by holding down the Shift key while you drag:
17. With the default build cursor, click on the upper circle to select it. Then click on the
Multi-State Symbol toolbar button:
Rev. 121908
Page 11
18. Click on the Tag Search button to select the T100_Sim_Vol tag. Review step
11 for the details of tag selection. Change the Color for State 1 to green (State 2
will default to red). Change the Values for State 1 to be <= 90. Finally, click
the OK button:
Rev. 121908
Page 12
19. Repeat steps 20 & 21 for the lower circle. This time however, specify a Values for
State 1 of <= 10. Specify the color of State 1 to be red, and that of State
2 to be green. Use the State drop-down box to select the state to edit:
20. Select the Bar toolbar button:
21. Using the Bar tool, drag a rectangle which exactly covers the box portion of the tank:
Rev. 121908
Page 13
22. Click the Tag Search button to select the tag T100_Sim_Vol, then click OK:
23. With the Bar object you just drew still selected, click the Drawing Color toolbar
button:
24. Change the Line and Background colors to None and then click the OK button:
Rev. 121908
Page 14
25. Click on the stem of the stirrer and on the Arrange menu, choose the Bring To
Front command:
26. Repeat step 25 with the Stirred tank label. You will have to click twice (slowly, not
double-clicking) to select the text label beneath the Bar we added on top:
27. Save the file.

28. Click the Run button and observe the function of the display and Dynamic Elements
youve added
Exercise continues on next page (leave your display open and in Run mode)
Rev. 121908
Page 15
PART C More with ProcessBook

1. In ProcessBook, select Tools-Preferences:
2. Select the Trend tab and review the items listed. These settings determine the
Default settings for trends added to ProcessBook displays:
Rev. 121908
Page 16
3. Change the Start Plot Scale from *-8 Hour to *-5 Minutes:
4.
Click OK to accept the changes and close the Preferences dialog box.
5. If you wanted to add a trend to your current ProcessBook display, you could do so with the
standard trend button youve used several times already (dont actually do this):
6. Instead, this time click on the T100_Sim_Vol value on your running Processbook display:
7. Be sure your display is in the Run mode. If not, change to Run mode and then re-click on
the T100_Sim_Vol value. Then, click the Trend Display icon on the toolbar:
Rev. 121908
Page 17
8. You should get an instant Ad Hoc trend of the selected tag:
9. Close the Ad Hoc trend. Click the value again and then click the Tag Properties icon:
10. You should get a property window for this tag as follows:
Rev. 121908
Page 18
11. Add two additional Value objects to your display assigned to tags of your choice:
12. With all three values selected (either rubber-band the cursor around them or use ctrlclicks), create an Ad Hoc trend.
13. With all three values selected, select Tag Properties. You should see a drop-down list
letting you select each of the tags, one at a time, to view their attributes.
Rev. 121908
Lesson 24
Inserting ProcessBook Displays in View SE via
ActiveView
What You Will Learn
How to extract individual ProcessBook displays from a

ProcessBook workbook and embed them inside a
FactoryTalk View display.
FactoryTalk Historian ActiveView provides the ability to embed fully interactive ProcessBook
displays in any ActiveX container. ActiveView provides a utility to extract individual displays
from a ProcessBook workbook. It also produces an HTML file which attempts to recreate the
general structure of the original workbook file.
Rev. 121908
Lesson 24 Inserting ProcessBook Displays in View SE via ActiveView
Page 2
PART A USING ACTIVEVIEW VIA INTERNET EXPLORER

Note: If using FactoryTalk Historian version 2.1, start with step 1 below. If using version
2.0, please skip steps 1-5 and start on step 6.
1. Verify that you are on the VM-HIST-1 image:
2. In FactoryTalk Administration Console, right-click on Production Historian and select

Properties:
3. On the Licensing tab, assign an activation to AVIEW (ActiveView)
Rev. 121908
Page 3
4. After clicking OK, close the FactoryTalk Administration Console.

5. Reboot the VM-HIST-1 image (Start Shutdown Restart). You can continue with this
exercise while the image is restarting.
6. In order to use ActiveView there are some client files that need to be installed on the client
computer to facilitate communication with the Historian server. There is not a separate
installer for the client files so we need to run the full ActiveView installation on the VMDATA-1 image to load the required client components. Verify that you are on the VMDATA-1 image by checking for the following in the upper-left corner:
7. Run the setup.exe located in the FactoryTalk Historian SE_AV installation folder.
(Ask instructor for exact location)
8. Select the Install Historian ActiveView option:
Rev. 121908
Page 4
9. Proceed through the installation wizard and select a Typical setup when prompted:
10. When prompted, reboot:
11. While the image is rebooting, switch to the VM-HIST-1 image:
Rev. 121908
Page 5
15. Use the Open icon on the toolbar to open the file Trends.PIW which you created in
an earlier exercise. If you did not complete the earlier exercise, instead open the
PBDEMO.PIW file located in C:\Program Files\Rockwell
Software\FactoryTalk Historian\Server\PIPC\Procbook:
16. Leaving open the Trends.PIW file, open the EXPORT.PDI file located in:
a. C:\Program Files\Rockwell Software\FactoryTalk
Historian\Server\PIPC\ACVIEW\WebDev:
Rev. 121908
Page 6
17. Specify an Export Path of C:\Inetpub\wwwroot and then click the OK

button. Note that in a real world deployment we would use a specific virtual site. For the
basic class it is simpler and quicker to just use the root site.
18. When completed, click the Close button and then close the ProcessBook application:
20. Open Internet Explorer:
Rev. 121908
Page 7
21. Set the address to: http://vmhttp://vm-histhist-1/PBhome.htm
22. Click on the Simple Trend. Note that the first time you use ActiveView per session it
you may see a blank white box or one containing connecting message while it tries to
connect to the historian server. This is normal. Just wait a minute while the connection is
established:
Rev. 121908
Page 8
23. After the connection is established, the ProcessBook displays will display and be fully
interactive. You can switch to other displays without experiencing the initial connection
delay:
Rev. 121908
Page 9
PART B USING ACTIVEVIEW IN VIEW SE DISPLAY

1. Now we will use ActiveView to embed a ProcessBook display in a FactoryTalk View SE
display. Launch FactoryTalk View Studio:
2. When prompted, select the Site Edition (Network) application type and click
Continue:
3. Open the InstaCorp application:
Rev. 121908
Page 10
4. Open the MixingHMI display process overview by double-clicking on its entry:
5. If you saved a trend object on the display in an earlier exercise, delete it now:
Rev. 121908
Page 11
6. Use the ActiveX Control object to draw a box in some empty space:
7. Select the PI ActiveView Control from the list and click the OK button:
Rev. 121908
Page 12
8. Double-click on the ActiveX to bring up the configuration dialog:
9. Leave the entry on the Server Ini tab blank. On the Display URL tab, enter a
Display URL of: http://VM-HIST-1/MULTI-TRENDS.PDI. Click the OK
button. If you did not complete the earlier exercise and exported the PBDEMO.PIW instead,
use a URL of: http://VM-HIST-1/Pulp Prep.PDI:
Rev. 121908
Page 13
10. Switch the FactoryTalk View display to test mode by clicking on the Test
Display toolbar button:
11. You now have a fully interactive ProcessBook display embedded in FactoryTalk View.
After you have experimented with the display, close all the applications. This exercise is
finished:
Rev. 121908
Page 14
Rev. 121908
Lesson 25
Using ProcessBook Data Sets
What You Will Learn
How to use ProcessBooks data sets to produce values and

trends based on locally calculated data.
FactroyTalk Historian ProcessBook data sets provide a means of producing locally calculated
data. Data sets can perform flexible calculations on dynamic data which can be trended or
displayed like any other historian data point. The calculations are local to the ProcessBook
workbook and provide an ideal place to prototype calculations which once finalized can later be
moved to server side calculation mechanisms like performance equations.
Rev. 121908
Lesson 25 Using ProcessBook Data Sets
Page 2
PART A CALCULATIONS ON SINGLE TAG

image:
Rev. 121908
Page 3
6. Select new ProcessBook Display (.pdi) File, set the Display Name to
Test, and click the OK button:
7. Select the Data Sets command on the Tools menu:
Rev. 121908
Page 4
8. In the Data Sets dialog, click on the New button and choose the PI
Calculation sub-type:
9. Set the data set Name to LEVEL and the Description to Tank Level. Set the
Tag or Expression to the tag SINUSOID and the Interval to 1h then
Rev. 121908
Page 5
10. Close the Data Sets dialog by clicking the Close button:
11. Change to build mode by selecting the Build button on the toolbar (your ProcessBook
may already be in build mode):
Rev. 121908
Page 6
14. Use the drop-down to the right of the Tag Search button to select a PI
Calculation:
Rev. 121908
Page 7
15. First, select LEVEL from the Datasets list. Next, select from the Columns the
Average, Minimum, and Maximum columns. Finally, click the OK button:
Rev. 121908
Page 8
16. Change the Start Time to *-12 Hour and then click the OK button:
17. Examine the effect of the data set calculations on the SINUSOID tag. Notice how the
summary calculations that we selected are performed on an hourly basis as configured by the
Interval setting. (note that the below trend is showing 12 hours of dataif your
Historian Server has not been constantly archiving data over the last 12 hours, your trend
may have only a portion of such data).:
Rev. 121908
Page 9
PART B CALCULATIONS WITH MULTIPLE TAGS

We will now explore using Data Sets to perform custom calculations utilizing multiple tags.
1. Use the Open icon on the toolbar to open the file Ex12 Data Sets.PDI located
in the class files folder:
2. Again, select the Data Sets entry on the Tools menu:
3. Notice that the Data Sets dialog is again empty. This is because the data sets we
previously created are local to the file in which they were created. Click on the New
button and choose the PI Calculation sub-type:
Rev. 121908
Page 10
4. On the PI Calculation Data dialog, set the following values:

a. Name:
PRODUCTA
b. Description:
% Product A
c. Tag or Expression:
'CDT158' / ('CDT158' +
'BA:TEMP.1') * 100
d. Column Label:
% Product A
5. Back in the Data Sets dialog, click on the Close button:
Rev. 121908
Page 11
7. Click on the Value toolbar button:
8. Use the Value tool and click on the area beneath the % Product A label:
Rev. 121908
Page 12
9. Select PI Calculation from the drop-down to the right of the Tag Search
button:
Rev. 121908
Page 13
10. Select PRODUCTA from the Datasets list. Next select % Product A from the
Columns list. Finally, click the OK button:
Rev. 121908
Page 14
12. Notice that the tank outlet now displays the current percentage of Product A:
13. With the Build cursor selected, double-click on the empty Plot-0:
Rev. 121908
Page 15
14. Select PI Calculation from the drop-down to the right of the Tag Search
button:
15. Select PRODUCTA from the Datasets list. Next select % Product A from the
Columns list. Finally, click the OK button:
Rev. 121908
Page 16
17. Now you can enjoy a live updating trend of the calculated product A percentage:
Close ProcessBook. This exercise has been completed.
Rev. 121908
Lesson 26
Using ProcessBook Relative Displays
What You Will Learn
How to use contexts from the Module Database to build

single ProcessBook displays which can apply to multiple
units.
Using Module Contexts from the Module Database we are able configure ProcessBook displays
against properties and aliases of units. Once these displays are associated with one or more
module units, the display will automatically populate with data from the chosen context.
Rev. 121908
Lesson 26 Using ProcessBook Relative Displays
Page 2
Exercise:
image:
2. Open System Management Tools and click on the Module Database in the Operation area:
3. Expand the VM-HIST-1 and Modules trees in the right-hand window. Note that there is a
%OSI Module already there. FactoryTalk Historian uses the Modules in this area for
internal storage and configuration of several different thing, including Interfaces:
Rev. 121908
Page 3
4. If a Module named Reactor Section already exists, please skip to step 6. Otherwise, create
this module by right-clicking on Modules and select New:
5. Enter Module name of Reactor Section and then click OK:
Rev. 121908
Page 4
6. Right-click on the Reactor Section Module that appears and select New Module:
7. Name the Module Reactor 1 and click OK. This portion of the Module Database should
now look like this (other item(s) might be listed of Reactor Section already existed):
8. Right-click on Reactor 1 and select New Alias:
Rev. 121908
Page 5
9. Enter an Alias Name of Concentration, select the VM-HIST-1 Server, use the Search
button to select the tag BA:CONC.1 and finally click OK:
10. If in this section you expand Reactor 1 and Aliases, your Reactor Section should now look
like the following:
11. Right-click on Reactor 1 two more times and add the following additional Aliases:
o Level, using tag BA:LEVEL.1
o Temperature, using tag BA:TEMP.1
12. When you have finished the above step, your Module should now look like this:
Rev. 121908
Page 6
13. Now we want to add some Properties to the Reactor 1 Module. Right-click on Reactor 1
and select New Property:
14. Name the property Height, select Data Type of Float and enter property value of 4:
15. After clicking OK, right-click on Reactor 1 and add another property of Radius, using
Data Type of Float and value of 2.2. The Module should now look like this:
Rev. 121908
Page 7
16. Now we will copy and paste the Reactor 1 Module to create a Module 2. Right-click on
Reactor 1 and select Copy:
17. Right-click on Reactor Section and click Paste Value Hierarchy:
18. If you expand the items you will see Copy of Reactor 1 has been added with the same
Aliases and Names as Reactor 1:
Rev. 121908
Page 8
19. One at a time, right-click on each of the items in this new Copy of Reactor 1 module and
edit as follows:
o Change name of the Copy of Reactor 1 module to Reactor 2
o Change the tag defined in the Concentration alias to SINUSOID
o Change the tag defined in the Level alias to SINUSOIDU
o Change the tag defined in the Temperature alias to CDT158
o Change value defined in the Height property to 5
o Change value defined in the Radius property to 2
20. The Module Database should now look like this, with the changes listed above made to the
aliases and properties:
21. Close the System Management Tools. Note: The next time you open the System
Management Tools, the list of Modules will be re-alphabetized and Reactor 1 will be listed
above Reactor 2.
Rev. 121908
Page 9
23. When prompted, accept the VM-HIST-1 server and then close the PBDEMO.PIW file that
opens at default and dont save changes.
25. Select a Type of ProcessBook Display (.pdi) File, set the Display
Name to Test and click the OK button:
26. Make sure that you are in Build mode and select the Symbol Library toolbar
button:
27. Drag a box in some empty space:
Rev. 121908
Page 10
28. Select a tank from the Tanks symbol library. Note: You can pick whichever tank you
wish, but if you want your display to match the display shown later in this exercise, you
should pick the Simple tank system 2 tank toward the bottom of the Tank library which
looks like this:
29. On the Tools menu, select the Add Module entry on the Module Context
sub-menu:
Rev. 121908
Page 11
30. Use ctrl-clicks to select both Reactor 1 and Reactor 2. Next click the > button
to add them both to the Selected Modules list. Finally click the OK button:
31. Click the Value toolbar button:
32. First, select Reactor 1 on the left part of the screen under Available Modules. Then, click
on the Value toolbar button and finally click on the background to the right of the tank to
initiate the dynamic value dialog:
Rev. 121908
Page 12
33. In the Format options, select a display location of Top for the Tag attribute. Next,
select the Module Context entry from the drop-down to the right of the Tag
Search button:
34. From the Properties category, select the Height entry. Next, click the >
button. Finally, click the OK button:
Rev. 121908
Page 13
36. Repeat steps 32 through 35 to add the Radius property and the Level,
Concentration, and Temperature aliases:
37. Click the Bar toolbar button and then drag a rectangle over the tank:
Rev. 121908
Page 14
38. Select Module Context from the drop-down to the right of the Tag Search
button:
39. Click on the Level alias, then the > button, and finally the OK button:
Rev. 121908
Page 15
41. Click on the Value toolbar button and then click on the background below the tank:
Rev. 121908
Page 16
42. In the Format options, select a display location of (None) for the Tag attribute.
Next, select the Module Context entry from the drop-down to the right of the Tag
Search button:
43. Select the Current Context checkbox and then click the OK button:
Rev. 121908
Page 17
45. Select the Trend toolbar button and drag a rectangle on the background below the tank:
Rev. 121908
Page 18
46. Select the Module Context entry from the drop-down to the right of the Tag
Search button:
47. Click on the Teperature alias, then the > button, and finally the OK button:
Rev. 121908
Page 19
48. Change the Start time to *-1 Hour and then click the OK button:
Rev. 121908
Page 20
49. Change back to Run mode and try changing the active context to Reactor 2:
50. After you have finished exploring your module relative display, close ProcessBook. This
exercise has been completed.
Rev. 121908
Lesson 27
Configuring and Using ProcessBook SQC
What You Will Learn
How to use the PI SQC add-in to configure control charts in

ProcessBook and perform common SQC calculations.
The PI SQC (Statistical Quality Control) add-in for ProcessBook provides a client side SQC
mechanism for FactoryTalk Historian. With the add-in, users can flexibly configure SQC
control charts. These charts can have advanced filtering, perform SQC statistical calculations,
and even check data points against SQC alarm conditions.
Rev. 121908
Lesson 27 Configuring and Using ProcessBook SQC
Page 2
Exercise:
1. Verify that you are on the VMVM-HISTHIST-1 image by checking the hostname on the background
image:
3. Click the Open toolbar button and open the file Ex16
Ex16 - ProcessBook SQC
Setup.xls
Setup.xls located in the class files folder (ask instructor for exact location):
4. Choose the Export Tags entry on the PI-SMT menu:
Rev. 121908
Page 3
7. Close Excel and run the PI SQC installer (PISQC_3_0_15_7_.msi) located in the
Additional Installs class file directory (ask instructor for exact location).
Rev. 121908
Page 4
8. Continue through the installation wizard until the process is finished:
10. If prompted, select the VM-HIST-1 Server and then close the PBDEMO.PIW file that
opens at default.
11. Use the Open icon on the toolbar to open the file Ex16a
Ex16a SQC.PDI
SQC.PDI located in the
class files folder:
12. Click OK to select the VM-HIST-1 Server:
Rev. 121908
Page 5
13. Verify that you are in Run mode and then explore the interactive SQC chart:
14. Drag a rectangle on the data plot to zoom in to the selected area:
15. Click the Revert Time Ranges toolbar button to undo the zoom:
Rev. 121908
Page 6
16. Double-click on the chart control to maximize it. Double-click on it again to return it to its
original size and location:
17. Use the One Time Period Back and One Time Period Forward toolbar
buttons to scroll through the data (may have to wait a few minutes if you get a No or not
enough data points or Not enough samples message):
18. Use the Scroll Time bar to free scroll through the data:
19. Use the set time range button to look at a specific period of data:
Rev. 121908
Page 7
20. Set the time span from *-4 Hour to * and click the OK button:
21. Use the Trend Cursor to explore the data values:
22. Double-click on the Exercise 1: [Individuals] title bar to bring up the

Statistics Window:
Rev. 121908
Page 8
23. Examine the various statistics and information available, eventually selecting the Plot
Data option and click on the Save Data To File button:
24. Save the data as sqcdata.txt

sqcdata.txt
sqcdata.txt in the My Documents folder:
Rev. 121908
Page 9
25. Close the Statistics Window and open the sqcdata.txt

sqcdata.txt
sqcdata.txt file in Notepad:
26. When you are done examining the available statistics, close Notepad and close the
ProcessBook display file (NOT ProcessBook itself).
Rev. 121908
Page 10
28. Select new ProcessBook Display (.pdi) File, set the Display Name to
Ex16
Ex16 - XBar
XBar, and click the OK button:
29. Switch to Build mode and then click on the SQC Chart toolbar button:
30. Drag a rectangle on the background to create an SQC Chart:
Rev. 121908
Page 11
31. On the General tab, set the following fields (and click OK):
o Chart Title: X-Bar Control Chart
o Chart Type: X - Bar
o Chart Tag:
stationary1
32. Click the Save toolbar button:
Rev. 121908
Page 12
33. Click the Save button to save this display to My Documents:
34. Take some time to explore your recently created SQC chart. When you are ready, use the
Save As command on the File menu:
Rev. 121908
Page 13
35. Set the new name to Ex16

Ex16 Moving Avg.PDI
Avg.PDI and then click the Save button:
36. Double-click the chart to return to the configuration dialog (must be in Build mode):
Rev. 121908
Page 14
37. On the General tab, set the Chart Title to Moving Avg Control Chart.
Next change the Chart Type to Moving Average. Finally click on the
Sample tab:
38. On the Sample tab, set the Sample Size to 5 and then click OK button:
Rev. 121908
Page 15
39. Click the Save toolbar button:
40. Take some time to experiment with the SQC chart.

41. When ready, first close the current PDI. Then, reopen the Ex16
Ex16 XBar.PDI
XBar.PDI file:
Rev. 121908
Page 16
42. Use the Save As command on the File menu:
43. Set the new name to Ex16

Ex16 XBar Time Sampled.PDI
Sampled.PDI
PDI and then click the Save
button:
Rev. 121908
Page 17
45. We want to change the sampling algorithm. We want to take two samples every ten minutes
starting on 5 and 6 minutes after the hour. On the Sample tab, make the following
changes:
Calculation Basis to Time
Calculation Period to 00:10:00
Sample Period to 00:01:00
Start Time of Sample to 00:05:00
Finally, click the OK button:
46. Click the Save button on the toolbar:
Rev. 121908
Page 18
47. Take some time to play with the SQC chart. When you are done, close the current PDI and
then open the file Ex16b
Ex16b SQC.PDI
SQC.PDI located in the class files folder:
Rev. 121908
Page 19
49. On the Sample tab, use the Tag Search button to select the
stationary3_filter tag and set the Filter Equation to :
stationary3_filter = 1
Then click the Check Syntax button:
50. Click OK to acknowledge that the filter equation is correct. Then, click OK to close the
PI-SQC Chart Definition dialog:
Rev. 121908
Page 20
51. Change to Run mode and use a Trend Cursor to view the values in the chart. No
values greater than 31.9 or less than 29.1 should appear:
52. Save the file and then close ProcessBook. This exercise has been completed.
Rev. 121908
Lesson 28
Using DataLink Sampled vs. Compressed Data
What You Will Learn
How to use DataLinks data retrieval functions and what the

difference is between sampled and compressed data.
FactoryTalk Historian DataLink provides many different methods to retrieve data. A

fundamental difference in many of the functions is whether you are retrieving sampled or
compressed data. Sampled data is regularly spaced data where interpolated values are returned if
there is not a recorded value at a particular timestamp. Compressed data is simply the actual
recorded values that were archived. This exercise demonstrates the difference, but begins with
an introduction to displaying data from FactoryTalk Historian in an Excel spreadsheet using
DataLink.
Rev. 121908
Lesson 28 Using DataLink Sampled vs Compressed Data
Page 2
Part A DataLink Introduction

image:
3. Enter text into the spreadsheet and widen rows as appropriate to create a spreadsheet
similar to the following:
4. Click in the cell under the text Temperature; and then select PI Current Value:
Rev. 121908
Page 3
5. In the dialog box that appears, click the Search button to the right of the Tagnames(s)
field:
6. On the Tag Search dialog that appears, click the Search button (may have to click twice):
Rev. 121908
Page 4
7. Click on the T100_Demo_Temp.PV tag and then click OK:
8. Click time at left. Then, click OK:
Rev. 121908
Page 5
9. You should have the current value of the T100_DemoTemp.PV tag with timestamp
displayed such as the following. Note: if one or more of your cells filled with number signs
(##########), widen out the cell to make more room for the information to fit.
10. This Current Value will not dynamically update, but notice if you press F9, whether this
cell is selected or not, the current value link will update (try it). Note that at times the tags
value may not be changing for many seconds in a row, so if the value doesnt change when
you press F9, please wait a few seconds and try again.
11. Now, select the cell under the Last Minute: text and select Compressed Data (Start
Time/End Time)
Rev. 121908
Page 6
12. Make the following entries:

Search and select the same T100_Demo_Temp.PV tag
Start Time of *
End Time of *-1m
Hide count
Show timestamps
Then, click OK
13. Your spreadsheet should now be showing the last minutes worth of data from the archive.
Note that although this tag might be configured with a 1 second scan class, based on times
when the tags value isnt changing and also exception and compressions settings, there is
not likely to be data archived every second (below graphic only showing partial data):
Rev. 121908
Page 7
14. Notice that pressing F9 will continue to update the single Current Value on the
spreadsheet, but seems to have no effect on updating the Compressed Data (Start Time /
End Time) array. A special key combination of Ctrl Alt Shift F9 will update this and
other arrays you might add, as well as the single Current Value field. Please try this key
combination to verify.
15. Select the cell under the cell containing Last 10 Values Archived and select PI
Compressed Data (Start Time/Number)
16. Make the following choices:
Select same T100_Demo_Temp.PV tag

Start time of *
Number of Values of 10
Select backwards in time
Show timestamps
Click OK
Rev. 121908
Page 8
17. You should see the last 10 values archived displayed. This new series of data, as well as the
other data on your spreadsheet, should update with Ctrl Alt Shift F9.
Note: In the last dialog you selected a Start Time of *, which specifies now or current
time. You also selected backwards in time. This was necessary because otherwise the
entry would try to show data ahead of the Start Time, instead of data archived prior to the
Start Time. Perhaps fine if the start time was at some point in the past. However, by Start
Time of current or now, data ahead of that time would have to be data archived in the
future, predicted by FactoryTalk Historian. FactoryTalk Historian is good, but not that
good!
18. When satisfied with the spreadsheet results, close the spreadsheet and save to My
Documents as Temperature Report.xls.
Exercise continues on next page
Rev. 121908
Page 9
Part B DataLink Sampled vs. Compressed Data

image:
2. If not already running, launch Excel 2003:
3. Open the file Ex09 DL Samp Data.xls located in the class files directory (ask
your instructor for the specific location):
Rev. 121908
Page 10
4. Note the preloaded Start and End times in cells B3 and B4. Rather than static dates/time,
this spreadsheet is using a formula to enter yesterday (TODAY 1) at 9:00am as the start
time and yesterday at 9:01am as the end time. For the remainder of this lab to work
correctly, this exercise assumes your Historian Server was up and running and archiving data
between 9:00am and 9:01am the day before you are actually doing this exercise. If you do
not think data was being archived yesterday between these times, please modify the formula
to sometime when data was being archived and/or consult with your instructor for assistance.
5. Select cell B2 and then use the Tag Search command on the PI menu. Be
careful to not get the same named command on the PI-SMT menu.
Rev. 121908
Page 11
6. Set the Tag Mask to *Temp.PV and then click the Search button. Select the tag
InstaCorp.InstaSoap.Mixing:RSLinx Enterprise.CLX1.T1
100.Demo_Temp.PV then
Rev. 121908
Page 12
7. Select cell D26 and then use the Sampled Data command on the PI menu:
8. Begin filling in the required parameters by clicking on the cell picker _

_ button for the
Tagname(s) field:
Rev. 121908
Page 13
9. Click on cell B2 and then click the return to dialog button:
10. Check the show timestamps box, and then use the same technique detailed in steps 7 & 8 to
pick the following cells:
Start Time
B3
End Time
B4
Time Interval B5
Rev. 121908
Page 14
11. After you clicked the OK button, the Sampled Data columns should be filled in with
equally spaced data points between the start and end times.
12. Now click in cell G26 and then select the Compressed Data (Start Time/End
Time) command on the PI menu:
Rev. 121908
Page 15
13. Check both the hide count and show timestamps checkboxes. Use the
techniques detailed in steps 7 & 8 to pick the following cells:
Tagname(s) B2
Start Time B3
End Time
B4
14. The chart is now updated with both regularly sampled and archived (compressed) data points.
Notice the small discrepancies that can appear in the sampled data when a peak happens
between samples. The archived data provides a more accurate representation of what
actually occurred than what you see with periodically interpolated data points:
Rev. 121908
Page 16
15. Also note the difference in quantity of source data points. If you want to refresh the data,
you will need to right-click within the Compressed Data set and choose
Recalculate (Resize) PIDL Formula off the context menu.
Note: In this case, you wont see any difference in the data when you do a Recalculate since
the formula is requesting data between specific start and end times (data recorded between
(9:00am and 9:01am yesterday). Instead of specific start and end times, if you were using
variable start and end times like start of * (now) and end of *-10 Minutes (10 minutes
ago), every time you Recalculate you would be likely to get different data.
16. Close Microsoft Excel. This exercise has been completed.
Rev. 121908
Lesson 29
Using DataLink Archived Data and Digital Tags
What You Will Learn
How to use DataLinks retrieval of archived digital state

changes to calculate simple metrics.
In the previous exercise we explored the difference in sampled versus compressed retrieval of a
time-series process value. In this exercise we use the compressed data function to retrieve state
changes of a digital tag. By employing some Excel logic functions we can quickly calculate
some very basic metrics.
In this exercise we will be looking at the tag BA:Active.2 to determine the operating time
percentage for a batch pump.
Rev. 121908
Lesson 29 Using DataLink Archived Data and Digital Tags
Page 2
Exercise:
image:
3. Open the file Ex10 DL Comp Data.xls located in the class files directory (ask
your instructor for the specific location):
Rev. 121908
Page 3
4. Select cell B2 and then type BA:Active.2 in the cell:
5. Select cell A7 and then choose the Compressed Data (Start Time/Number)
command on the PI menu:
Rev. 121908
Page 4
6. Select the checkbox for show timestamps. Next, use the cell pick buttons _ as detailed
in Exercise 9, steps 7 & 8, to pick the following cells:
Tagname(s)
B2
Start Time
B3
Number of Values B4
Rev. 121908
Page 5
7. After you clicked the OK button, the Time and Status columns should have been
populated with state transition data. Select cell C8 and type in the formula:
=IF(B7=Active, A8-A7, 0)
8. Select cell C8 again and then click the Copy toolbar button:
Rev. 121908
Page 6
9. Now drag a selection box from cell C9 to C23 and then click the Paste toolbar icon:
10. The simple summation and division formulas will automatically calculate a running time
percentage. Close Excel. This exercise has been completed.
Rev. 121908
Lesson 30
Inserting DataLink Trend Objects
What You Will Learn
How to use DataLinks Trend Object for charting time-series

data from FactoryTalk Historian and Excel native data.
FactroyTalk Historian DataLink provides a Trend Object for Excel that has the capability of
charting data within Excel as well as data directly from FactoryTalk Historian. This exercise
will give you experience using that object with both kinds of data.
Rev. 121908
Lesson 30 Inserting DataLink Trend Objects
Page 2
Exercise:
image:
3. Open the file Ex11 DL Trend.xls located in the class files directory (ask your
instructor for the specific location):
Rev. 121908
Page 3
4. Begin by selecting cell C6 and then choose the Insert Trend command on the
PI menu:
5. On the Trend Add-in Wizard dialog, first switch the radio-button to Data from PI.
Next, use the cell picker _ button to select cell B5 for the Tag name. Finally, click
the Add -> button:
Rev. 121908
Page 4
6. Now switch the radio-button back to Data on worksheet. Select the checkbox for
First element is trace name. Use the cell picker _ button to select a data
range of cells A8 through B17. Click the Add -> button and then the Next >
button:
7. Select the Enable updates checkbox. Next, click the reference worksheet buttons for
both the Start Time and End Time:
Rev. 121908
Page 5
8. Use the cell pick _ buttons to select cell B2 for the Start Time and cell B3 for
the End Time. Click the Next > button:
9. Set the optional Trend title to Tank Levels and then click the Format
button:
Rev. 121908
Page 6
10. Select the Vertical Scale property. On the Options tab, change the Format
to General and the Position to Outside Left. Click the OK button:
Rev. 121908
Page 7
11. Click the Finish button:
12. Enjoy your interactive trend. Trend cursors are available just like in ProcessBook. Mouse
over data point pop-ups are also available:
13. Unlike a regular Excel chart, the DataLink Trend is fixed to a specific location on the
worksheet. You can move or resize the trend by selecting the appropriate option on the
trends right-click context menu:
14. Close Excel. This exercise has been completed.
Rev. 121908
Page 8
Rev. 121908
Lesson 31
Using DataLink Filtered Compressed Function
What You Will Learn
How to use the PI DataLink Calculated Data function
In this exercise you are going to use Excel and the FactoryTalk Historian DataLink Compressed
Data function with a filter expression to retrieve up to twenty Tank 100 temperature readings
from the last two minutes which are above an arbitrary limit of 149.
The two available Compressed Data functions are:
1. Compressed Data (start time/number)
Function: PINCompFilDat
Retrieves compressed data that satisfies a filter condition.
The user determines the initial date-time and the number of values to be returned.
2. Compressed Data (start time/end time)
Function: PICompFilDat
Retrieves compressed data based on a start time and an end time that satisfies a filter
condition.
For this exercise you will use the Compressed Data (start time/number) function.
Filter Expressions:
The following describes the syntax of valid filter expressions in FactoryTalk Historian
DataLink.
A filter expression uses the same arithmetic operators and functions as a calculation
expression. In addition, one or more relational operators are needed.
Relational operators are:
<
=
>
<=
<>
>=
less than
equal to
greater than
less than or equal to
not equal to
greater than or equal to
Rev. 121908
Lesson 31 Using DataLink Filtered Compressed Function
Page 2
Example: (abs('my:tag') >= 14.65)

The above expression evaluates to TRUE if the absolute value of the tag mytag is at least
14.65.
To comparing digital tags, use the digital state string itself. For example: ('my.tag' =
"Manual")
A filter expression may also contain logical operators such as:
AND returns TRUE if both arguments are TRUE

OR returns TRUE if at least one of the arguments is TRUE
NOT returns TRUE if argument is FALSE, and vice-versa
Example:
The following expression evaluates to TRUE if the value of the tag sinusoid is less than 45
and the square root of the value of the tag vdf1002 is greater than 2:
('sinusoid' < 45 and sqr('vdf1002') > 2)
Rev. 121908
Page 3
Exercise:
image.
2. Launch Excel.
3. Open the file: Exercise 5 - DataLink Filtered Compressed _Template.xls located in the
class files directory (ask your instructor for the specific location):
4. Select Cell B3.
Rev. 121908
Page 4
5. From the Excel PI menu, select Tag Search.
Note: Be careful to not get the same named command on the PI-SMT menu.
6. In the search Tag Mask field type *T100*PV then click Search.
7. Select the tag: InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Temp.PV
8. Click OK.
Rev. 121908
Page 5
9. The Tag Name field will display T100_Demo_Temp.PV with the current value below. If
the Current Value cell displays #NAME?, right-click on the cell, select Current
Value, then click OK on the dialog that appears.
10. To calculate the values for the last two minutes, enter a Start Time of: *-2m in cell B5.
11. In this exercise you are using the Filtered Compressed Data Number function, so do not enter
an End Time, just leave it blank.
12. Set the Number of Values to 20 (cell B7).
Before adding the Compressed Data function, you will copy the tag name to the clipboard.
The tag name is long and prone to error when typing by hand.
13. Select cell B3 and copy the tag name to the clipboard from the address bar (you will paste
this tag into a dialog box a few steps from now).
Rev. 121908
Page 6
14. Select cell A16 under the Start Time field.
15. From the PI menu, select Compressed Data (Start Time/Number)
16. Populate the Compressed Data (Start Time / Number) dialog using cell references by
clicking on the
icon and selecting the required cell as detailed below:
Tagname(s):
Start Time:
Number of Values:
Output cell:
Cell B3
Cell B5
Cell B7
Cell A16
17. To determine when T100_Demo_Temp is greater then 149, enter the following Filter
Expression:
'InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Temp.PV'>149
Note: There are single quotation marks around the tag address tag name. Instead of
typing, you may optionally paste the tag address copied in step 13 and add the end
quotation mark and >149 comparison.
Rev. 121908
Page 7
18. Verify the following options (be sure to select show timestamps) and click OK.
Rev. 121908
Page 8
19. Review the calculated data.
Note:
Pressing F9 key recalculates Excel dynamic time functions and the Current Value
function:
=Now(), =Today(), =PICurrVal()

Other DataLink functions based on these functions
Pressing CTRL+SHIFT+ALT+F9 simultaneously does the following:
Everything that F9 does

Recalculate other DataLink functions based on relative FTH time (i.e. '*', '*-3h')
Note: Ctrl-Alt-Shift-F9 includes the Ctrl-Alt key combination which may cause you to break
out of a full-screen VMWare session.
20. Save your work and close Excel.
Rev. 121908
Lesson 32
Using DataLink Calculated Data Function
What You Will Learn
How to use the PI DataLink Calculated Data function
In this exercise, you are going to use the Excel PI DataLink Calculated Data function to
calculate the T100 temperature (T100_Demo_Temp.PV) 5 minute average for a 1 hour period.
Then you will add the minimum and maximum calculated data, change the time interval, and
trend these average calculated averages.
Function: PICalcDat
Retrieves a calculated value for a given tag, in a specified time interval
Can retrieve the total, the minimum, the maximum, the standard deviation, the range, the
count, the average or the mean
Rev. 121908
Lesson 32 Using DataLink Calculated Data Function
Page 2
Verify that you are on the VM-HIST-1 image by checking the hostname on the background
image.
1. Launch Excel.
2. Open the file Exercise 6 DataLink Calculated Data_Template.xls located in the class
files directory (ask your instructor for the specific location):
3. Select Cell B3.
Rev. 121908
Page 3
4. From the Excel PI menu, select Tag Search.
5. In the search Tag Mask field type *T100* then Select Search.
6. Select the tag T100_Demo_Temp.PV, The full syntax is:
InstaCorp.InstaSoap.Mixing:RSLinx Enterprise:CLX1.T100_Demo_Temp.PV
7. Select OK.
Rev. 121908
Page 4
8. The Tag Name filed should now display T100_Demo_Temp.PV with the current value
below.
Note: FactoryTalk Historian DataLink is tightly integrated with Excel, so that excel cells can
be accessed as flexible parameters for the components from the DataLink menu. The
calculated data can more dynamic by linking it to cell based time specifications.
9. Enter a Start Time of *-1h (to calculate the values for the last hour from now)
10. Enter a End Time of * (Current time as of now)
11. Enter a Time Interval of 5m (interval period for the calculation data)
Note: These setting should return 12 calculated values (60m / 5m = 12)
12. To add the calculation data, in the calculated report area, select Cell A19 under the Start
Time field
Rev. 121908
Page 5
13. From the Excel PI menu, select Calculated Data
14. Enter the Get calculated values using cell references picker. For each parameter click on the
icon and select the required cell reference as detailed below:
Tag Name:
Start Time:
End Time:
Time Interval:
Output cell:
Cell B3
Cell B5
Cell B6
Cell B9
Cell A19
15. Set the Calculated Mode to Average and check show start and end times.
16. Verify the following options and then click OK.
Rev. 121908
Page 6
17. Review the calculated data.
Note:
function:


Note: Ctrl-Alt-Shift-F9 includes the Ctrl-Alt combination which might have an adverse effect in a
VMware session.
Rev. 121908
Page 7
18. Add the minimum and maximum calculated data using the procedure in steps 14 to 17 (as
above), but with the following modified options
Set the Calculated Mode to minimum / maximum and uncheck show start and end
times.
Set minimum output cell to D19 and maximum output cell to F19
Calculated Data for minimum values to be displayed in the Minimum column will appear
as follows:
Calculated Data for maximum values to be displayed in the Maximum column will appear
as follows:
Rev. 121908
Page 8
19. Review the calculated data, noting the repeating min and max calculated values.
20. As the T100 temperature is cycling between minimum and maximum in a given time period,
if the calculated time interval specified is larger then the temperature time cycle (going from
min to max), then the calculated values will be the same for each time interval. Change the
following:
Start Time of *-2m
Enter a Time Interval of 8s
Rev. 121908
Page 9
21. Note that though the calculated value is every 8 second now, only 12 row are returned (as
previous setting) instead of 15 (120s / 8s = 15). Select and right-click on all calculated arrays.
22. From the right-click context menu, select Recalculate (resize) PIDL Formula.
23. Select cell A39.

24. From the Excel PI menu, select Calculated Data and repeats steps 15 to 18, uncheck show
start time but check show end time. Click OK after verifying options:
Rev. 121908
Page 10
25. Review the calculated data, (similar as above).
26. Select Cell D38 and then from the Excel PI menu, select Insert Trend
27. Check the Data on Worksheet option button.

28. Click on the select cell
icon and select cell B39.
29. Click Add.

30. Check the Markers check box.
31. Click Next and then Finish.
Rev. 121908
Page 11
32. Review the trend.
33. Change the Start time and Time Interval.

34. Press CTRL+SHIFT+ALT+F9 to recalculate.
35. Review the calculated data, this completes this exercise.
Rev. 121908
Page 12
Rev. 121908
Lesson 33
Using DataLink Timed Filtered
What You Will Learn
How to use the PI DataLink Time Filtered to calculate the

operating time status
In this exercise you are going to use the Excel PI DataLink Time Filtered function to view the
status changes of a digital tag to determine over the last day and how much time in each hour
was spent in the active state. This method performs the calculation in a single step.
You will be using the tag BA:ACTIVE.2 to determine the active state time.
Function: PITimeFilter
Retrieves the amount of time where an expression is true
Rev. 121908
Lesson 33 Using DataLink Time Filtered Function
Page 2
Exercise:
image.
2. Launch Excel.
3. Open the file Exercise 08 DataLink Time Filtered_Template.xls located in the class files
directory (ask your instructor for the specific location):
Set the various time options

4. Enter a Start Time of *-1d in cell B6 (one day ago)
5. Enter a End Time of * in cell B7 (current time starting now)
6. Enter a Time Interval of 1h in cell B10 (interval period for the calculation data)
7. To configure the Time Unit, on the worksheet, select Cell B11.
Rev. 121908
Page 3
8. From the Excel Data menu, select Validation
9. For the validation criteria set Allow field to List.

10. In the Source field enter: seconds, minutes, hours, days and click OK.
11. Select Cell B11 and click the drop down list selector icon
and select minutes
Rev. 121908
Page 4
12. Next, add the expression that will be used in the Time Filtered function. Select cell B12 and
enter the expression:
BA:ACTIVE.2=Active
Note: The first two characters are Single Quotations, , with a single quotation after the tag
name and Double Quotations before and after Active, (the cell view only displays the 1st
single quotation character).
13. Verify the settings which will return 24 time filtered values (1 day / 1 hr).
14. In the data output area, select Cell A15 under the Data / Time.
15. From the Excel PI menu, select Time Filtered
Rev. 121908
16. For each parameter click on the

below:
Page 5
icon and select the required cell reference as detailed
Expression(s)
Cell B12
Start Time:
Cell B6
End Time:
Cell B7
Time Interval[opt.]:
Cell B10
Time Units:
Cell B11
Note: To be able to select the Time Units from a selected cell rather then from the
drop down list, click the cell icon
then click the cell picker icon
and select
Cell B11
Output cell:
Cell A15
Check show start time checkbox
Note: To be able to select the Time Units from a selected cell rather then from the drop down
then click the cell picker icon
and select Cell B11
list, click the cell icon
17. Verify the following options and then click OK
Rev. 121908
Page 6
18. Review the Time Filtered data.
Note:
function:


Rev. 121908
Page 7
19. Modify one or more of the time parameters (i.e. Start Time, End Time, Time Interval, and
Time Unit) and review the data.
o Right-click on cell A15 and select Recalculate (Resize) PIDL Formula on the context
menu
Note: If the time parameters modified result in increases in size of the output data area,
(more returned rows), then you may need to Recalculate (resize) PIDL Formula.
20. A Time Filtered expression can contain multiple conditions using the logical operators OR
and AND. Modify the expression to use the AND operator by entering:
BA.ACTIVE.2=Active AND 'Sinusoid'>30
Note: The difference in the calculation of time when this condition was met.
Rev. 121908
Page 8
21. Modify the expression to use the OR operator by entering:

BA.ACTIVE.2=Active OR 'Sinusoid'>30
22. Save your work and close Excel, this completes this exercise
Rev. 121908
Lesson 34
Using ACE Unit Conversion
What You Will Learn
How to utilize an Advanced Computing Engine (ACE)

calculation to perform a Unit Conversion
In this exercise, you will utilize an Advanced Computing Engine (ACE) calculation to perform
English to Metric system conversion for data points. The ideal situation would be to have this
calculation performed in the control system; however, this is not always feasible. You could
easily perform this calculation with a Performance Equation; the disadvantage to using a PE is
that you would have to replicate the equation and configuration in individual PEs for each data
point to convert. In contrast, ACE can use the module database to easily assign a single
definition of the calculation to multiple data points.
To expedite configuration of this exercise, you will be using point source L for all of our new
tags. You can easily tie these tags to control system tags using the FTLD2 interface. You may
choose to do this after you have completed the exercise.
Reference: PI-ACE User Guide C:\Program files\Rockwell Software\FactoryTalk

Historian\Server\PIPC\ACE\Help\PI ACE User Guide.pdf
Rev. 121908
Lesson 34 Using ACE - Unit Conversion
Page 2
Exercise:
image.
3. Expand the Points category and select the Point Builder SMT plug-in.
Rev. 121908
Page 3
5. Create two new points named MachA_Len_English and MachA_Len_Metric configured

as
Point Type Float32
Point Source - L
6. Using the Point Builder SMT plug-in, select the Archive Tab and for each of the two tags
just created in step 4 and configure the following:
Compressing Off
Turn Step On
Disable Exception Deviations 0 (Off)
Exception Max Time 0
Rev. 121908
Page 4
8. For the MachA_Len_English tag ONLY, set Archiving Off.
10. Launch Excel.
11. From the Excel PI-SMT menu, select Import Tags from the context menu.
Rev. 121908
Page 5
12. In the Import Tag dialog enter the following:
Set Tag Mask to MachA*
Set Point Source to L
Set Point Class to classic
13. Click the OK button to import the data
14. Click OK to acknowledge the results dialog.
Rev. 121908
Page 6
15. Two rows are returned, copy both rows and paste them twice for a total of 6 rows.
16. Modify the tag names in the tag columns, so that there are two MachB_* tag, two MachC_*,
two MachD_* tags.
17. Verify the following tag names:
18. To create the new tags, from the Excel PI-SMT menu, select Export Tags from the
context menu
Rev. 121908
Page 7
19. Change the Mode to Create

20. Click the OK button.
21. Click the OK button to acknowledge the results.

22. Switch back to the SMT and Expand the Operations category and select the Module
Database SMT plug-in.
23. Right-click on the Modules entry and select New to create a new module
Rev. 121908
Page 8
24. Enter Production Line into the Module Name field.
25. Right-click on the new Production Line module and select New Module to create a module
named Machine A.
26. Right-click on the Machine A module and create a new Alias.
Rev. 121908
Page 9
27. Set the following parameters:
Alias Name:
PI server:
Tag Name:
CutLen
VM-HIST-1
MachA_Len_English
28. Click OK
29. Right-click on the Machine A module and create another new Alias named MetricLen and
map it to the MachA_Len_Metric tag.
Rev. 121908
Page 10
30. Return to Excel and from the PI-SMT -> Module Database Builder menu; select Import
Items from the context menu.
31. Select the Production Line module.

32. Verify that the following options are selected and click OK.
Rev. 121908
Page 11
33. On the returned data, delete the x from the first column of the first row returned.
34. Copy the other three rows returned and paste them two times for a total of three sets of
Machine A entries.
35. Change the names of the three line sets to be Machine B, Machine C, and Machine D
36. Change the AliasDataSource (column T) to match the corresponding machine tags.
37. Delete column R (ModuleUniqueId)

38. Return to Excel and from the PI-SMT -> Module Database Builder menu; select Export
Items from the context menu to create these three new modules with associated aliases.
39. Select the PI-SMT - Module Database Builder menu, select the Export command.
40. Set the mode to Create, and click OK.
Rev. 121908
Page 12
41. Switch back to SMT and confirm that these three new modules with associated aliases have
been created. Select Module Database, SMT plug-in, and expand Modules under
Production Line and verify that each of the Machine modules and aliases have been created.
42. Open Visual Studio 2005.
43. On the Tools menu, select PIACEWizard -> New.
Rev. 121908
Page 13
44. In the PI ACE Wizard Page : Name page, enter Conversion into the PI ACE Executable
Name field and enter InToCm into the PI ACE Class Module Name.
45. Click Next.
46. Set the Context to \\VM-HIST-1\Production Line\Machine A by using the button

open the context window and set the context to Machine A.
to
47. Click Close.
Rev. 121908
Page 14
48. In the ACE Wizard Page 2/2: Tag Information for Conversion.InToCm page, click in the
Input Aliases Tag Name box and click the Alias Search button.
49. Verify that the Alias Search Context parameter is \\VM-HIST-1\Production Line\Machine
A, enter an asterisk * in the Alias field and click the Search button.
Rev. 121908
Page 15
50. Highlight the aliases tag CutLen and click OK.
51. Click in the Output Aliases Tag Name box and then the Alias Search button.
52. Verify that the Alias Search Context parameter is \\VM-HIST-1\Production Line\Machine
A. Enter an asterisk * in the Alias field and then click the Search button.
53. Highlight the aliases tag MetricLen and click OK.
Rev. 121908
Page 16
54. Click the Finish button.
55.
Add the following code to the ACECalculations() subroutine

If IsNumeric(CutLen.Value) Then
MetricLen.Value = CutLen.Value * 2.54
Else
MetricLen.SendDataToPI = False
End If
56. From the Tools menu, select the PIACEWizard -> Test command on the context menu
Rev. 121908
Page 17
57. Enter the following:
Set PI ACE Executable Name to Conversion
Set Class Module Name to InToCm
58. Click OK.
59. Click the Get Typical Values button followed by the Calculate Now button to evaluate the
Output Alias for correctness. Note: you might normally select Get Current Values and then
Calculate Now to test your application. However, in this case we just recently created the
CutLen tags and their current values would still be Pt Created. So, we will use the default
Typical Value of 50 which should result in a Metric equivalent of 127.
60. Close the test window.
Rev. 121908
Page 18
61. From the Tools menu, select the PIACEWizard -> Register command to register the ACE
Module.
62. Under Scheduling, check the Natural radio button.
63. Check the CutLen alias as the Trigger.
64. Click OK and Close the dialog.
65. Close Visual Studio 2005.

66. Launch the PI-ACE Manager, (located on the VM-HIST-1 desktop or double-click on the
PIACEManager.exe file found in C:\Program Files\Rockwell Software\FactoryTalk
Historian\Server\PIPC\ACE).
Rev. 121908
Page 19
67. Expand the Tree and right-click on the InToCm class and select the Add New Context
from the context menu.
68. In the Add/Edit Context properties dialog window, use the button
and select the Machine B module for the context.
to open the context
69. Click Close
Rev. 121908
Page 20
70. Under Scheduling, check the Natural radio button.

71. Check the CutLen alias as the trigger
72. Change Latency to 0 seconds, and click Save.
73. Repeat the previous three steps for Machine C and Machine D.
74. Right click on Machine A context and select Edit Shedule and Priority... from contextmenu
75. Change Latency to 0
76. Click Save button
Rev. 121908
Page 21
77. Verify the conversion Context is as shown below:
78. From the Administrative Tools - Services applet, start the PI-ACE 2.x Scheduler service.
Optionally change the service startup mode to Automatic.
79. Return to the ACE Manager and refresh the view and note that the modules should now be
green.
80. Use the SMT archive editor plug-in to insert a new value into one of the Mach?_Len_English
tags at the current time *.
81. Check that the Mach?_Len_Metric tag gets updated with the calculated value.
Rev. 121908
Page 22
Rev. 121908
Lesson 35
Using Reporting Services
What You Will Learn
How to create a basic Microsoft reporting services report for

reporting on FactoryTalk Historian data
In this exercise you will go through the process of creating a basic Microsoft reporting services
report which pulls data from FactoryTank Historian database.
SQL Server 2005 Reporting Services
SQL Server 2005 Reporting Services is a server-based reporting platform that can be used to
create and manage tabular, matrix, graphical, and free-form reports that contain data from
relational and multidimensional data sources. The reports can be viewed and managed over a
World Wide Web-based connection. Reporting Services includes the following core
components:
Complete set of tools that you can use to create, manage, and view reports
Report Server (NT Service) component that hosts and processes reports in a variety of
formats. These (output) formats include HTML, PDF, TIFF, Excel, CSV, and more.
One of the sources of data that Reporting Services can work with is OLEDB providers. The PI
OLEDB is pre-installed
Reporting Services detailed help can be found in MS SQL Server Books Online available at
http://www.microsoft.com/sql/default.mspx
Rev. 121908
Lesson 35 Using Reporting Services
Page 2
Exercise:
image.
2. This image has Microsoft SQL and Reporting Services installed, but at this point neither
service is running to save resources. Select Start Administrative Tools Services:
3. Locate the following two services, SQL Server and SQL Server Reporting Services:
Rev. 121908
Page 3
4. Right-click on each of these services (one at a time) and select Start

5. Once both services indicate Status of Started, close the Services Dialog Box.
6. Later in this exercise you will be using Microsoft Internet Explorer to view a report with data
from FactoryTalk Historian. In order to do so, there will need to be a Trust created. Open
the System Management Tools (SMT) and select Trusts:
7. In the right-hand window, click on the down-arrow next to the New button and select
Advanced:
Rev. 121908
Page 4
8. Fill out the form that appears as follows:
9. Select OK to add this Trust and then close the SMT.
Rev. 121908
Page 5
10. From the Start Menu, Launch the SQL Server Business Intelligence Development Studio
by selecting All Programs\Microsoft SQL Server 2005\SQL Server Business Intelligence
Development Studio.
11. On the File menu, point to New, and then click Project from the context menu
Rev. 121908
Page 6
12. In the Project types list, click Business Intelligence Projects.

13. In the Templates list, click Report Server Project.
14. In the Name field, enter FTH MSReport
15. Click OK to create the project.
16. The FTH MSReport solution will be displayed momentarily in VS Solution Explorer view
(a window on the right side):
Rev. 121908
Page 7
17. You need to specify the target Server URL for the project. If the properties page is not
automatically displayed when creating the report, in the Solution Explorer, right-click FTH
MSReport and click Properties.
18. Set the target Server URL to http://localhost/ReportServer

19. Click OK
Rev. 121908
Page 8
In order to collect data from the Historian server, you need to create a connection
to the Historian server. In this exercise, you will add a shared data source via the
PI OLEDB.
20. Right-click the "Shared Data Sources" folder and select the "Add New Data Source" entry.'
21. The Shared Data Source dialog box appears.

22. Enter PIOLEDB in the Name field.
23. Select OLE DB from the Type: drop-down list.
24. Click the Edit button and fill in the PI OLEDB connection properties.
Rev. 121908
Page 9
25. Select OLE Provider to PI OLE DB Provider from the drop-down list
26. Enter VM-HIST-1 into Server or file name field.
27. Enter Administrator into the User name field and enter rockwell into Password field.
28. Check the box Allow saving password
29. Verify that the following options are selected and entered correctly in the image below.
30. Click Test Connection

31. Verify that the connection succeeded and click OK, and OK again
Rev. 121908
Page 10
32. Verify that the connection string is populated.
33. Select the Credentials tab and explicitly specify login account Administrator and Password
rockwell (otherwise you may get errors when running the report).
34. Verify the following options and click OK.
Rev. 121908
Page 11
35. After the data source is defined, Report Designer creates a dataset (you named it PI OLEDB)
and it displays the generic query designer
36. Create the report definition file, in the Solution Explorer, right-click Reports, point to Add,
and click New Item.
37. Select Report Wizard.

38. In Name field, leave the default Report1.rdl
39. Click Add.
Rev. 121908
Page 12
40. The Report Wizard welcome page will be displayed. Click Next:
41. Verify the shared data source is set to PIOLEDB.

42. Click Next.
43. In the design query type the following:

SELECT tag, time, value, status
FROM piarchive..picomp
WHERE tag LIKE ? AND time >= ? AND time <= ?
ORDER BY tag, time
Rev. 121908
Page 13
44. Click Next.
45. Select the report type as Tabular.

46. Click Next.
Rev. 121908
Page 14
47. In the report design table, select tag and then click the Page tab to move tag into the page
display field.
48. Select time and click the Group tab to move time into the Group display field.
49. Select Value and Status and click the Details tab to move value and status into the
details display field.
50. Verify that the following groups have been configured.
51. Click Next.
52. Select the default Stepped and click Next.

53. Select the default Slate and click Next.
54. In Report Name field, leave the default report name Report1.
55. Click Finish.
Rev. 121908
Page 15
56. A view opens that contains Data, Layout, and Preview tabs; the report opens in Layout
view.
57. From the Report menu, select Report Parameters:
Rev. 121908
Page 16
58. Select Parameter 1

59. Set Data Type to String
60. Set Prompt to Tag Mask
61. Set the default value radio button to Null
62. Repeat the above parameter configuration steps for parameter 2 and 3 with the following
settings
64. Set Data Type to DateTime
65. Set Prompt to Start Time
68. Set Data Type to DateTime
69. Set Prompt to End Time
Rev. 121908
Page 17
71. Click the OK button to close the report parameter dialog

72. From the VS design view window select the Preview tab to preview Report1.
73. Verify the build complete with 0 errors and warnings (0utput window bottom of VS)
74. Set the parameters to the following:
Tag Mask: *T100*.PV
Start Time: Date and Time of 5 minutes ago (for example, 3/12/2008 6:33:00 AM)
End Time: Date of tomorrow
75. Click View Report

Note: It will take some time to generate the report
Rev. 121908
Page 18
76. You need to deploy the report. In the Solution Explorer, right-click Report1.rdl and click
Deploy.
77. Verify that the Deploy succeeded, it may take some time (0utput window bottom of VS)
Rev. 121908
Page 19
78. To view the report, launch Internet Explorer.

79. In the address combo box enter http://VM-HIST-1/Reports
80. If asked to log in, enter Administrator into the User name field and enter rockwell into
Password field.
81. Select FTH MSReport.
82. Select Report1
Rev. 121908
Page 20
83. Set the parameters to the following:
Tag Mask: *T100*.PV
Start Time: Date and Time of 5 minutes ago (for example 3/12/2008 8:33:00 PM)
End Time: Date of tomorrow
84. Click View Report
85. Scroll down within the window to view the report that you have created
This exercise is complete.
Rev. 121908
Appendix A
Installing Activation and FactoryTalk Services Platform
Install FactoryTalk Activation Server
verify that you have the VM-DATA-1 image selected

browse to the FTA folder (your instructor will give you the location)
double click on the FTAServer folder

double click on the setup,exe file
Rev. 121908
Appendix A Installing Activation and FactoryTalk Services Platform
Page 2

click Run

click Next
Rev. 121908
Page 3

select the Modify option
click Next

click Next
Rev. 121908
Page 4

click Install

click Finish
Rev. 121908
Page 5
Install FactoryTalk Activation Client

verify that you have the VM-HIST-1 image selected

browse to the FTA folder (your instructor will give you the location)
double click on the FTAClient folder

double click on the setup,exe file
Rev. 121908
Page 6

click Run

click Next
Rev. 121908
Page 7

select the Modify option
click Next

click Next
Rev. 121908
Page 8

click Install

click Finish
Rev. 121908
Page 9
Configure FactoryTalk Activation Server

verify that you have the VM-HIST-1 image selected

from the Start menu select the FactoryTalk Activation Tool

verify that you have no current activations
select the Settings tab
Rev. 121908
Page 10

click the New icon

click the Browse icon
Rev. 121908
Page 11

select VM-DATA-1 from the My Network Places tree
click OK

Important: You must move off of the @VM-DATA-1 select to save that selection
move off the @VM-DATA-1 select by selecting the C:\Program Files---------selection

select the Current Activations tab
Rev. 121908
Page 12

verify that you have current activations
Rev. 121908
Page 13
Loading and Configuring the

FactoryTalk Services
The FactoryTalk Services Platform is an underlying architecture and set of services that
software products, which are part of a FactoryTalk suite, can build upon. Products
participating in the FactoryTalk suite include FactoryTalk View, RSLinx, RSLogix,
FactoryTalk Batch, FactoryTalk AssetCentre, and FactoryTalk Transaction Manager,
among others.
The FactoryTalk Services Platform:
Provides common services (such as diagnostic messages, health monitoring

services, access to real-time data) and shares plant resources (such as tags and
graphic displays) throughout a production facility
Allows defining plant-floor resources once, and then allows simultaneous access
to those resources across product boundaries
Supports centralized security services
Supports centralized alarms and events services
Parts of the FactoryTalk Services Platform

With each coordinated release, more Rockwell Automation products join the FactoryTalk
suite by building on the FactoryTalk platform and integrating more of the FactoryTalk
components and services. All of these components and services install together as a
platform, integrated into each FactoryTalk products software install process. The
FactoryTalk Services Platform currently includes:
FactoryTalk Directory
FactoryTalk Directory allows products to share a common address book, which finds and
provides access to plant-floor resources, such as data tags and graphic displays.
The FactoryTalk Services Platform includes two separate directories: a Local Directory
and a Network Directory. In a Local Directory, a Directory Server, all project
information, and all participating software products are located on a single computer.
Local applications cannot be shared across a network. A Network Directory organizes
project information from multiple FactoryTalk products across multiple computers on a
network.
Rev. 121908
Page 14
FactoryTalk Security
Both the Local Directory and the Network Directory support centralized security
services, managed by FactoryTalk Security.
FactoryTalk Live Data

FactoryTalk Live Data manages connections between FactoryTalk products and data
servers. It reads values from and writes values to OPC-DA servers (OLE for Process
Control - Data Access) and Live Data servers on behalf of client software products, such
as FactoryTalk View and FactoryTalk Transaction Manager.
FactoryTalk Diagnostics
FactoryTalk Diagnostics collects and provides access to activity, status, warning, and
error messages generated throughout a FactoryTalk system.

FactoryTalk Administration Console is an optional, stand-alone tool that allows
configuring, managing, and securing applications.
Other FactoryTalk services

Rockwell Automation products, which are part of the FactoryTalk suite, can also take
advantage of additional FactoryTalk services. These services do not install as part of the
FactoryTalk Services Platform, but instead, install along with certain software products.
FactoryTalk Activation
FactoryTalk Activation provides a secure, software-based system for activating
Rockwell Automation software products and managing software activation files.
FactoryTalk Activation services install along with each participating product.
FactoryTalk Alarms and Events

FactoryTalk Alarms and Events is a set of integrated services and software
components that allow multiple FactoryTalk products to participate together in a
common, consistent view of alarms and events throughout an application.
Rev. 121908
Page 15
What is a FactoryTalk system?

A FactoryTalk system is comprised of software products, services, and hardware
devices participating together and sharing the same FactoryTalk Directory and
FactoryTalk services.
For example, a FactoryTalk system may be as simple as FactoryTalk Services Platform,
FactoryTalk View, RSLinx Classic, and RSLogix 5 all installed on the same computer,
communicating with a single programmable logic controller, and all participating in the
same Local Application held in a Local Directory.
A FactoryTalk system may be much more complex, with software products and hardware
devices participating in multiple Network Applications distributed across a network, all
sharing the same Network Directory and FactoryTalk services.
Rev. 121908
Page 16
A single computer can host both a Local Directory and a Network Directory. The two
directories are completely separate and do not share any information. If you use both
directories, then that single computer participates in two separate FactoryTalk systems.
In the Network Directory example above, the directory hosts two Network Applications:
one named Waste Water and the other named Water Distribution. All of the areas, data
servers, HMI servers, device servers, and alarm and event servers organized within each
application are specific to that application. None of the application-specific information is
shared with any other application in the directory. However, all of the information and
settings organized within the System folder, such as security settings, system policies,
product policies, user accounts, and so on, apply to all applications held in the directory.
For example, if we create a new area in the WasteWater application and add a new Tag
Alarm and Event Server, the change does not affect the Water Distribution application.
However, if we make a change to a Security Policy, the change applies to both the
WasteWater application and the Water Distribution application. The setting would also
apply to any other new applications created in the future in this same Network Directory.
FactoryTalk Directory
The FactoryTalk Directory is the centerpiece of the FactoryTalk Services Platform.
FactoryTalk Directory provides a central lookup service for all products participating in
an application. Rather than a traditional system design with multiple, duplicated
databases or a central, replicated database, FactoryTalk Directory references tags and
other system elements from multiple data sourcesand makes the information available
to clients through a lookup service.
Tags are stored in their original environments, such as logic controllers, and graphic
displays are stored in the HMI servers where they are created. Yet all of this information
is available, without duplication, to any FactoryTalk product participating in an
application.
Rev. 121908
Page 17
For example, at workstation 1, a logic programmer programs PLC tags using RSLogix
and then saves the project. At workstation 2, an engineer using FactoryTalk View SE has
immediate access to the tags created in the PLC program, without creating an HMI tag
database. Tags are available for immediate use anywhere within the application, even
before the logic program is downloaded to the controller. As the logic program is edited,
most tag information is updated, and new tags are available immediately across the
system.
With Logix5000 controllers, tags reside within the hardware itself. With Allen-Bradley
PLC-5 and SLC 500 devices, and with third-party controllers, tags reside within data
servers, such as RSLinx Classic and RSLinx Enterprise. Tags are not held within a
common database, nor are they duplicated in multiple databases. Instead, the FactoryTalk
Directory references tags from their source locations and passes the information on to the
software products that need it, such as FactoryTalk View SE and FactoryTalk
Transaction Manager.
A single computer can host two directories

The FactoryTalk Services Platform installs and configures two completely separate and
independent directories: a Local Directory and a Network Directory. Each directory
can hold multiple applications.
In a Local Directory, all project information and security settings are located on a
single computer, and the FactoryTalk system cannot be shared across a network
or from the Network Directory on the same computer. Products such as
FactoryTalk View SE (Local) and FactoryTalk View ME use the Local Directory.
A Network Directory organizes project information and security settings from

multiple FactoryTalk products across multiple computers on a network. Products
such as FactoryTalk View SE and FactoryTalk Transaction Manager use the
Network Directory.
Which directory you need depends upon which software products you plan to use and
whether you plan to work in a stand-alone or a networked environment. Consult your
product documentation for details.
Two directories on one computer

Different software products have different requirements for the FactoryTalk Directory.
Both directories are installed and configured as part of installing the FactoryTalk Services
Platform. Which directory you need depends upon which software products you plan to
use and whether you plan to work in a stand-alone or a networked environment.
For example, if you use FactoryTalk View SE or FactoryTalk Transaction Manager, you
will use the Network Directory to create and manage Network Applications. If you use
Rev. 121908
Page 18
FactoryTalk View ME, you will use the Local Directory to and manage Local
Applications. Other products, such as RSLogix 5, RSLogix 500, and RSLinx Enterprise,
allow you to use either directory. Consult your product documentation for details. See
Choosing a FactoryTalk Directory.
Even though a Local Directory and a Network Directory reside on the same computer, all
of their project information and security settings remain completely separate and cannot
be shared, including:
User accounts, passwords, security permissions
System-wide policy settings, including security and audit policies
Project information, such as applications, areas, and their contents
The graphic below shows three computers. Each computer has both a Local Directory
and a Network Directory configured. Each directory holds objects, which represent
project information, such as applications, references to data servers, and security settings,
including user accounts. In each Local Directory, these project objects can be accessed
only by software products installed on that same local computer. The Network Directory,
however, can share references to its objects across a network.
For example, suppose each colored icon above represents the project information and
security settings that are part of a FactoryTalk system. The Local Directories on each
computer hold completely separate sets of information (represented by the green, blue,
and yellow icons). In the case of the Network Directory, all client computers that point to
the same Network Directory Server computer share the same set of information across
the network (represented by the orange icons).
Suppose we run FactoryTalk Administration Console on Computer 3, log on to the
Network Directory, and create a user account named "Terry" with the password
"OpenSesame." The change is actually made in the Network Directory Server, held on
Rev. 121908
Page 19
Computer 1, and immediately reflected on each Network Directory client computer.

"Terry" can now log on to the Network Directory from any of the three computers.
Now suppose we create a user account named "Terry" with the password "OpenSesame"
in each Local Directory on every computer. Even though the user name and password are
the same, each user account is a separate object in each Local Directory.
If we change the password in the Local Directory on Computer 1, the change does not
affect the user account held in the Network Directory Server on the same computer, nor
does it affect the user accounts held in the Local Directories on computers 2 and 3.
In the same way, you might have multiple user accounts, all with the same user name and
password, on your computer at home. For example, you might log on to your Windows
system with the user name "HomeAccount" and password "NorthAndSouth." You might
create accounts and use the same user name and password to log on to your local bank, a
bill-paying service, several online shopping accounts, and your online broker. Suppose
you log on to your bank and change your password to "EastAndWest." This change will
not affect the password for your Windows system, bill-paying service, online shopping
accounts, or online broker, because each of these accounts is separate, even though each
has the same user name and password.
Rev. 121908
Page 20
Install FactoryTalk Services Platform (FTSP)

The FactoryTalk Services Platform (FTSP) software is installed as a prerequisite for all
FactoryTalk enabled software such as:
FTAssetCentre, FT Transaction Manager, FTView, FTMetrics and FT Historian

SE
Note: The FTSP has been installed on both the VM-HIST-1 and VM-DATA-1 images. Both
images are using the FT Network Directory on the VM-DATA-1 image.
prior to installing the FTSP software there are no Rockwell Software components in
the C:\documents and Setting\Default User\Application Data directory.
Rev. 121908
Page 21
open Windows explorer and go to E:\Ft Transaction Manager\9.00.00.54\
double click Setup.exe
click on Required Steps
Rev. 121908
Page 22
click on Step 1 Check Operating System
verify the operating system and internet explorer checks succeeded
click OK
click OK
8.
click on Step 4 Install FactoryTalk Services Platform

Do the following steps:
click Next
Rev. 121908
Page 23
select the I Accept the terms in the licensing agreement option
click Next
check the Install FactoryTalk Administration Console
click Next
Note: This option may not appear when loading different version of the FTSP
Rev. 121908
Page 24
click Install
NOTE: the following dialog will appear during the install process
Rev. 121908
Page 25
NOTE: the following dialog will appear during the install process
click Finish
Rev. 121908
Page 26
after the FTSP installation is complete a Rockwell and WFCU directory have been
added to the C:\documents and Setting\Default User\Application Data directory.
under the C:\documents and Setting\Default User\Application Data\Rockwell

directory two additional folders have been added, RNA Client and RNAServer
Rev. 121908
Page 27
under the C:\documents and Setting\Default User\Application

Data\Rockwell\RNAServer directory three additional folders were added
Backups
Global
Local

Data\Rockwell\RNAServer\Global directory two files and one directory were
added.
folder RnaStore
files $Global.RnaD and $System,RnaD
Rev. 121908
Page 28

Data\Rockwell\RNAServer\Local directory two files and one folder were added.
folder RnaStore
files $Local.RnaD and $System.RnaD
Under the C:\documents and Setting\Default User\Application

Data\Rockwell\RNAClient directory two additional folders were added Global and
Local
Rev. 121908
Page 29

Data\Rockwell\RNAClient\Global directory two files and two folders were added.
folders RnaStore and RnaTemp
files $Global.RnaD and $System.RnaD

Data\Rockwell\RNAClient\Local directory two files and two folders were added.
folders RnaStore and RnaTemp
files $Local.RnaD and $System.RnaD
Rev. 121908
Page 30
open the Factory Talk Administration Console from Start>All Programs>Rockwell

Software>Factory Talk Administration Console
select the Network option
click OK
Rev. 121908
Page 31
review the default User Groups and Users in the Network directory
review default Security Setting for the All Users in the Network Directory
check on screen shot
Rev. 121908
Page 32
close the Factory Talk Console and re-open it
select the Local option
click OK
review the default User Groups and Users in the Local directory
Rev. 121908
Page 33
review default Security Setting for the Administrators in the Local Directory
This completes the installation of the FTSP and a review of the default folders, files,
User Groups, Users and Network security settings for both the Network and Local
directories
Rev. 121908
Page 34
This page is intentionally left blank
Rev. 121908
Appendix B
Creating a FactoryTalk Application
What You Will Learn
How to use the FactoryTalk Administration Console to

create a FactoryTalk Application
Create a FactoryTalk Application
Add folders for Line
Add folders for Machines
Add Data Servers for each Machine
FactoryTalk Applications
In a FactoryTalk Directory, an application organizes elements such as data servers, alarm
and event servers, HMI servers and project information, and makes all of that information
available to all software products and computers participating in that same application.
A FactoryTalk Network Directory can manage any number of separate Network
applications. A FactoryTalk Local Directory can manager any number of separate Local
applications.
As part of developing a FactoryTalk system, log on to either a Network Directory or a
Local Directory, create an application, and then create optional areas and add
FactoryTalk View SE servers, data servers, and optional alarm and event servers.
If you are using FactoryTalk View SE, you must use FactoryTalk View Studio to
add and configure FactoryTalk View SE servers. With FactoryTalk View Studio,
you can work with only one application at a time.
If you are not using FactoryTalk View, you can use the FactoryTalk
Administration Console to create applications, optional areas, and servers. With
FactoryTalk Administration Console, you can see and interact with all of the
applications managed by a directory.
Exploring a Network Directory with multiple applications

A FactoryTalk Directory holds any number of applications, stores information about each
application and makes that information available to FactoryTalk products and services.
FactoryTalk Directory also stores system-wide information, such as security settings,
product policies and system policies. This system information is shared among all of the
applications in the directory but is not shared across multiple directories.
Rev. 121908
Appendix B Creating a FactoryTalk Application
Page 2
If you are using FactoryTalk Administration Console to create and manage applications,
the Explorer window lists all of the applications that are contained in the FactoryTalk
Directory. FactoryTalk View Studio, however, provides access to only one application at
a time.
Areas
Areas organize and subdivide applications in a Network Directory into logical or physical
divisions. The root of an application can contain only one HMI server. To add additional
HMI servers to an application, create a separate area for each server. Each area can
contain only one HMI server. Areas are not available in a Local Directory.
Servers
OPC data servers
Data servers provide tags contained in OPC-DA (Data Access) servers. Every
vendor's OPC data server is different. Clients that need access to tags, such as
FactoryTalk View SE and FactoryTalk Transaction Manager, use FactoryTalk
Directory to locate the computers that are hosting OPC-DA 2.0 compliant data
servers.
Data server information is stored as part of an application. Adding a data server to
an application or an area provides a link between a hardware device containing
tags (via the OPC server's defined topics) and the FactoryTalk Directory.
Rockwell Automation Device Servers (RSLinx Enterprise)
To access both tag values and alarm and event values from a Logix5000
processor, use direct references to the processor through a Rockwell Automation
Device Server (RSLinx Enterprise).
Tag Alarm and Event Servers
To use FactoryTalk Alarms and Events services with older hardware devices, use
Tag Alarm and Event Servers to set up tag-based alarm monitoring. Use tag-based
alarm monitoring with PLC or SLC controllers, Logix5000 controllers with older
firmware that does not support the new alarm instructions, or third-party devices
communicating through OPC-DA servers. Tag Alarm and Event Servers monitor
tags for alarm conditions and publish event information to Alarms and Events
Services. From there, alarm and event information is routed through the alarms
and events system for display and logging.
FactoryTalk View SE Servers (HMI servers)
A Network application in FactoryTalk View SE must have at least one HMI
server. A Local application can have no more than one HMI server. HMI clients
use FactoryTalk Directory to locate the computers that are hosting HMI Servers.
Use FactoryTalk View Studio to add HMI servers. HMI servers store and serve
HMI projects that contain graphic displays, log models, HMI tags and other
Rev. 121908
Page 3
services to clients such as FactoryTalk View Studio and FactoryTalk View SE

Clients.
System settings
The System folder contains settings that affect all of the applications held in a
FactoryTalk Directory. These settings include system policies, product policies, user
accounts and user groups, computers and computer groups and database connections. See
About multiple System folders in FactoryTalk View.
The Networks and Devices tree shows information about the control hardware devices,
managed by RSLinx Classic, that are connected to a local computer. If you have
administrative access to the FactoryTalk Directory, you can secure each network or
device separately to make them available to the applications in the FactoryTalk
Directory. The same networks and devices appear in the Network Directory and Local
Directory trees, but the networks and devices can be secured differently in each directory.
Tip: If tags appear to be missing from the FactoryTalk View Tag Browser, right-click the
application icon in the browser window and then select Refresh All Folders. For more
information and step-by-step instructions, see the FactoryTalk View Studio Help.
Rev. 121908
Page 4
Create a FactoryTalk Application

On the VM-CLX image, from the Start button Select All Programs\Rockwell
Software\FactoryTalk Administration Console

Select the Network option and
Click OK
Rev. 121908
Page 5

At the Network level right-mouse click
Select New Application

In the Name text box enter MyApp
Click OK

Right mouse click on MyApp
Select New Area
Rev. 121908
Page 6

In the name text box enter Line1
Click OK

Right-mouse click on Line1 and select New Area

In the name text box enter Mach3
Click OK
Rev. 121908
Page 7

Right mouse click on Mach3 and select Add New Server\Rockwell Automation
Device Server (RSLinx Enterprise)

In the name text box enter Mach3_Ent
Click OK
Rev. 121908
Page 8

Expand the Mach3 folder to Communication Setup
Double click on Communication Setup

Click Add
Change the shortcut name to FTHistorian
Browse to and select 3, 1789-L60/A, FTHistorian
Note: you may have to right mouse click and turn on start browsing
Click Apply
Click OK
Rev. 121908
Page 9

Note: The computer names, paths and file names may vary depending on the VMWare
Image or computer that you are using. Your instructor will give you the correct information.
Set the Offline tag file to FTHistorian1.ACD using the browse button
Click Open
Rev. 121908
Page 10

Verify that the FTHistorian1.ACD file was selected
Click OK

Click Yes

Close the FT Administrative Console
Rev. 121908
Appendix C
FactoryTalk Historian Time Format

Relative Time
Relative time is some number of days, hours, minutes, or seconds. The leading sign (+ or
-) is required.
+/- d | h | m | s
The default starting point for relative time is usually the current time. Therefore, a time of
-8h is eight hours before the current time. Fractional times may be entered. For example,
use - 1.5d for one and one-half days. Only a single operator is supported, + or -. For
example, this is not supported:
-1d+1h
Absolute Time
Absolute times have one of the following formats:
DD-MMM-YY hh:mm:ss.ssss - day-month-year hour:minute:second
* - current time.
T - 00:00:00 on the current day (TODAY)
Y - 00:00:00on the previous day (YESTERDAY)
Monday - 00:00:00 on the most recent Monday
Sun,Mon,Tue,Wed,Thu,Fri,Sat - 00:00:00 on the most recent Sunday, Monday,
..., Saturday
For the DD-MMM-YY hh:mm:ss.ssss format, if any of the date fields are left out,
they default to the current date. Time fields default to 00.
Examples
25 - 00:00:00 on the 25th of the current month
25-Aug-86 - 00:00:00 on that date
8: - 08:00:00 on the current date
25 8 - 08:00:00 on the 25th of the current month
21:30:01.02 - 9:30:01.0200 PM on the current date
Caution should be used with the default settings. Here are some examples of timestamps
that may be confusing.
8: - 08:00:00 on the current date
:8 - 08:00:00 on the current date
::8 - 00:08:00 on the current date
:::8 - 00:00:08 on the current date
0:8 - 00:08:00 on the current date
Continued on next page
Rev. 121908
Appendix C FactoryTalk Historian Time Format
Page 2
The confusion comes from the ambiguity in the first two examples above. Following this
theme, when minutes are added to the next examples, the time stamps are still similar.
8:01 - 08:01:00 on the current date
:8:01 - 08:01:00 on the current date
The difference in the two notations is evident when a date is added to the time. When a
date is added to the front of the time the default notation is hh:mm:ss.ssss not
:hh:mm:ss.ssss.
2 8: - 08:00:00 on the 2nd of the current month
2 :8 - 00:08:00 on the 2nd of the current month
2 ::8 - 00:00:08 on the 2nd of the current month
If extra colons and times are added that is greater than the given DD-MMM-YY
hh:mm:ss.ssss format the last part of the time will be disregarded.
2 :::8 - 00:00:00 on the 2nd of the current month
2 :::8 - 00:00:00 on the 2nd of the current month
2 8:01:30 - 08:01:30 on the 2nd of the current month
2 :8:01:30 - 00:08:01 on the 2nd of the current month
A value for the seconds must be used if sub-seconds are used. Hence caution should also
be used when considering timestamps containing sub-seconds.
8::30.01 - 08:00:30.0100 on the current date
:8::30.01 - 08:00:30.0100 on the current date
14 :8::30.01 - 00:08:00 on the 14th of the current month
Here are examples of timestamps that do not work.
8:30.01 - Ambiguous, 8 could be minutes or hours
:8:30.01 - Ambiguous, 8 could be minutes or hours
Combined Formats
Combined time scales use both an absolute and a relative time. The absolute part of the
time can be *, T, Y, or a day of the week.
Examples
T + 8h - 08:00:00 AM on the current day (today)
Y - 8h - 04:00:00 PM on the day before yesterday
Mon + 14.5h - 02:30:00 PM on the most recent Monday
- 1h - One hour ago
Rev. 121908
Appendix D
What You Will Learn
How to install the components of FactoryTalk Historian

utilizing a distributed data collection interface node. These
components you will install include:
FactoryTalk Historian Distributed Interface
FactoryTalk Historian Security Components
The Virtual Machines

In this class there are three virtual machine images being used. The first is called VM-DATA1. This image is the data server for the class. It is already loaded with the following software
products:
FactoryTalk Network Directory
FactoryTalk Activation Server
FactoryTalk View SE
FactoryTalk Historian Interface
The second virtual machine image is called VM-CLX. This image will serve as the CLX
Controller(s) that we will be collecting data from. It is already loaded with the following
software products:
FactoryTalk Platform Services
RSLogix 5000
SoftLogix 5800
RSLinx Classic
RSLinx Enterprise
The third virtual machine image is called VM-HIST-1. This image will be loaded with the
FactoryTalk Historian server software. It is already loaded with the following software products:
Microsoft Excel
FactoryTalk Historian SE
FactoryTalk Historian SE is a scalable and integrated solution. It redefines the options for
manufacturers who want to maximize their ability to collect and analyze process data. Use
Rev. 121908
Appendix D Installing FactoryTalk Historian (Version 2.0)
Page 2
FactoryTalk Historian to capture data across your enterprise while serving the data to plant
applications. This allows for fast and reliable data capture at the controller level and at high
speeds and low intervals. FactoryTalk Historian SE provides the capability to collect, store,
analyze, and visualize data using a powerful engine and a set of reporting tools such as timeseries trends, bar charts, piecharts, pareto and tabular trends, and an easy method of generating
reports using Microsoft Excel. It also uses compressed storage data algorithms to contain a vast
amount of data in a small format. You can retrieve data spanning a long or short time span
quickly. FactoryTalk Historian SE is closely integrated with the following Rockwell
Automations
FactoryTalk Services Platform and Applications.
FactoryTalk LiveData (FTLD): A direct data interface to FactoryTalk LiveData delivers

native FTLD data directly to Historian without requiring intermediate interfaces and
standards such as OPC.
FactoryTalk Directory: FactoryTalk Historian uses FactoryTalk Directory to look up data

points for configuring points to historize. The directory is also used for auto-discovering
controller data sources and tags in the initial configuration process.
FactoryTalk Security: By integrating FactoryTalk Historian with FactoryTalk Security,

all users and user groups can be maintained centrally, and a single sign-on is fully
supported.
FactoryTalk Activation: FactoryTalk Historian is activated by Rockwell Automation's

central licensing system based on the FactoryTalk Activation Server.
FactoryTalk Diagnostics: Because of FactoryTalk Historian's close integration with

FactoryTalk Diagnostics, all system and diagnostics messages from FactoryTalk
Historian are centrally stored and maintained in the FactoryTalk central Diagnostics
database.
FactoryTalk Audit: All FactoryTalk Historian server auditing messages are stored and
available in the FactoryTalk central Audit database.
FactoryTalk View SE Trending: FactoryTalk View Supervisory Edition natively trends

data from FactoryTalk Historian.
Ordering Information
FactoryTalk Historian servers include:
FactoryTalk CD
FactoryTalk Activation CD
Source Tag-limited license for the FactoryTalk Historian server
License for one FactoryTalk Historian DataLink Excel reporting client
Rev. 121908
Page 3
FactoryTalk Historian servers ship with FactoryTalk Activation, and do not include an activation
diskette. Instructions for activating software via the Internet are included. FactoryTalk Historian
server licenses are additive. For example, if 1400 Reporting Tags are required, purchasing and
installing both a 500 and 1000 Reporting Tags license on a single server will activate as a 1500
Reporting Tags server.
Server connections are separated in two types: one for connecting to Rockwell Automation data
sources, primarily through FactoryTalk Live Data, and one for connecting to third-party data
sources using OPC or any of the 450 native connectors for the historian.
Catalog Number
9518-HSERA500
9518-HSERA1K
9518-HSERA2K5
9518-HSERA5K
9518-HSERA10K
9518-HSERA20K
9518-HSERA50K
9518-HSERA100K
Description
FactoryTalk Historian Site Edition 500 Live Data Tags
Catalog Number
9518-HSE3RD500
9518-HSE3RD1K
9518-HSE3RD2K5
9518-HSE3RD5K
9518-HSE3RD10K
9518-HSE3RD20K
9518-HSE3RD50K
Description
FactoryTalk Historian Site Edition 500 Third Party Data Tags
Authoring Client
The FactoryTalk Historian Authoring Client licenses allow a user, using either the FactoryTalk
Historian DataLink Client, to develop Microsoft Excel reports, or the FactoryTalk Historian
ProcessBook Client, to develop graphical analytics to either stand alone or to be integrated into
FactoryTalk View screens. Purchase one Authoring Client license for each user who will be
performing FactoryTalk Historian authoring functions.
Catalog Number
9518-HPBENE
9518-HDLENE
9518-HDLENF
Description
FactoryTalk Historian ProcessBook Authoring Client
FactoryTalk Historian DataLink Excel Reporting tool
FactoryTalk Historian DataLink Excel Reporting tool - Concurrent
License
Rev. 121908
Page 4
FactoryTalk Historian Client license for FactoryTalk View

The FactoryTalk Historian Client license for FactoryTalk View allows users to view FactoryTalk
Historian trends and to view FactoryTalk Historian ProcessBook content in FactoryTalk View
screens.
Purchase a Single-User Runtime Client license for each user who will access the system
concurrently.
Catalog Number
9518-HCLNTENF
Description
FactoryTalk Historian Client License for FactoryTalk View
FactoryTalk Historian Integration with FactoryTalk Batch

The FactoryTalk Historian EVT interface allows the historian to capture FactoryTalk Batch
events from the FactoryTalk Batch Journal or Event log file. As the events are written to the
journal by FactoryTalk Batch, the historian is picking up those events, and adding them to the
FactoryTalk Historian Batch Database. These events can then be visualized as event frames on
top of the time-series data.
The BatchView add-in can be used to visualize these events in either ProcessBook displays or in
Excel.
Catalog Number
9518-HINEVT1U
9518-HINEVT3U
9518-HINEVT10U
9518-HINEVT30U
9518-HINEVT60U
9518HBAVENE
9518HBAVENF
Description
BatchView add-in for FactoryTalk Batch Database single user
BatchView add-in for FactoryTalk Batch Database concurrent license
System Requirements
The hardware and software required with FactoryTalk Historian Site Edition depends on the
demands an application places on the system. The greater the demand, the more powerful a
system is required. For large or complex applications, use computers with faster CPUs and more
RAM. In any application, faster CPUs and more RAM will result in better performance. In
addition, there should always be sufficient disk space to provide virtual memory that is at least
twice the size of the physical RAM.
Windows 2000 Operating System

If you are using a Windows 2000 operating system, MDAC 2.7 or above must be installed
before FactoryTalk Historian can be installed.
Rev. 121908
Page 5

Minimum: Intel Pentium D, 3.2Ghz, 1GB RAM
Operating Systems:
purposes only)
Minimum: Intel Pentium Xeon, 3.0Ghz, 2GB RAM
Operating Systems:
Microsoft Windows 2000 Server with Service Pack 4 or
purposes only)
Minimum: Intel Pentium Xeon dual processor, 3.4Ghz, 4GB RAM
Operating Systems:
purposes only)
FactoryTalk Historian Site Edition Interface Node
Minimum: Intel Celeron D, 3.0Ghz, 512MB RAM
Operating Systems:
Minimum: Intel Pentium III, 600MHz, 512MB RAM

Recommended: Intel Pentium 4, 2GHz or higher, 1GB RAM or more
Operating Systems:
Rev. 121908
Page 6
FactoryTalk Historian Site Edition Network Client
Minimum: Intel Pentium III, 600Mhz, 512MB RAM

Recommended: Intel Celeron, 3GHz or higher, 1GB RAM or more
Operating Systems:
Note: FactoryTalk Administration Console is tested on operating systems installed from original
Microsoft media only. Some Microsoft operating system service packs and hot fixes are not
compatible with FactoryTalk Historian Site Edition. To find out if there are any problems with a
particular Microsoft update, click the "FactoryTalk Historian SE Operating System and Service
Pack Compatibility" link in the Rockwell Automation Knowledgebase
Choosing a Setup Type

Historian Server Installation
This choice installs the Historian server, the System Management Tools, the Interface
Configuration Utility, and the LiveData interface. This will install the FactoryTalk Historian
system and its components and the FactoryTalk LiveData interface in one box so that the system
can be started with minimal configuration.
Historian Interface Installation
This choice installs the System Management Tools, the Interface Configuration Utility, the
LiveData interface, and the buffer management service. Select this option if you are installing
the interface tools on a machine other than the machine hosting the server.
Selected Components and Tools
This option allows you to choose which components you want to install. If you choose this
option, the Custom Setup screen displays when you click [Next].
Rev. 121908
Page 7
PART A - Install the FactoryTalk Historian Server Component

At this point we are ready to install the FactoryTalk Historian server component on the VMHIST-1 image. This image is pointing to the FactoryTalk Network Directory located on VMDATA-1.
2. Log in to the VM-HIST-1 image. Use the following credentials:

o User name:
Administrator
o Password:
rockwell
3. Run the setup.exe located in the FactoryTalk Historian SE installation folder.
(Instructor will provide specific path to supplemental class files)
4. Select the Install FactoryTalk Historian option:
Rev. 121908
Page 8
5. Click Next
Rev. 121908
Page 9
8. Proceed through the wizard and select the Historian Server Installation
type:
Rev. 121908
Page 10
9. Verify that you have selected the Server installation by checking that the
FactoryTalk Historian Server component is listed in the New or
Upgraded Components list and then click Install: This will install all of the
components.
o DEselect Install FactoryTalk Activation
o Click Finish
Rev. 121908
Page 11
Rev. 121908
Page 12
Grant FactoryTalk Historian Administration Privileges

In this class we will be using the local machine Administrator account to administrate the
FactoryTalk Historian system. We must grant the Administrator account the appropriate
privileges in the FactoryTalk Historian system. We accomplish this by making the Windows
Administrators user group a member of the new FTHAdministrators group.
1. Verify that you are on the VM-DATA-1 image by checking for the following in the upper-left
corner:
2. Open the FactoryTalk Administration Console, Start All Programs Rockwell Software
FactoryTalk Administration Console:
3. Select Network and click OK
Rev. 121908
Page 13
4. Open the FTHAdministrators group by double-clicking on its entry under the User
Groups folder:
5. Click on the Add button:
Rev. 121908
Page 14
6. Click on the Windows Administrators group, and click the OK button:
Close the FactoryTalk Administration Console:
Rev. 121908
Page 15
Verify FTH Server is running using About SDK

corner:
2. Next we want to adjust the default connection timeout setting. Launch the AboutPISDK utility:
Rev. 121908
Page 16
4. Change the Connection Timeout to 30 seconds, click the Save button, and
close the application. Note we are using 30 seconds for training purposes. In your actual
applications you may set this value lower or higher:
5. Check the VM-HIST-1 check box and verify the connection and click Close
Rev. 121908
Page 17
Verify Current and Archived Data using the SMT


Check the VM-HIST-1 check box
Expand the Data folder and select Current Values
Select the Search Icon
Rev. 121908
Page 18

Click the Search button (you may have to click it twice)

Select the SINUSOID tag
click OK

Verify that the SINUSOID tag has a value
Rev. 121908
Page 19

From the Data folder select the Recorded Values

Rev. 121908
Page 20

Select the SINUSOID tag
click OK

Click the Get Events button

Verify that you have Archived values
Rev. 121908
Page 21

Expand the Operations folder and select Licensing
Select the Resources folder and select PointSourceLimit FTLD
Verify the you have FT Activations for the FTLD interface

Close the System Management Tools (SMT)
Rev. 121908
Page 22
Register the FactoryTalk Historian and Local Interface

Now that the server and local interface have been installed, we need to register these components
with the FactoryTalk Directory. In the first release of FactoryTalk Historian SE, this
configuration must be performed on the computer containing the Historian Server.
4. Notice that network application data servers are not fully configurable from this image since
RSLinx Enterprise has not been installed locally:
Rev. 121908
Page 23
5. Expand the System | Connections tree. Right-click on the Historical Data folder
and select the New Historian Server Connection entry.
6. Click the Test Server Connection button:
Rev. 121908
Page 24
7. Verify that the server was found and then click the Finish button. Do NOT click
Next at this time (the Next button will open the Discover Historian Points wizard which
we will cover in a separate exercise).
8. Verify that the Production Historian and FTLD1 interface now show up under the
Historical Data folder: Right mouse click on FTLD1 and select Properties
Rev. 121908
Page 25
9. From the Startup type combo box select Automatic and click the apply button
Rev. 121908
Page 26
10. Click the Start button. Once the service has started click OK
Rev. 121908
Page 27
[Optional] Create VM-HIST-1 Desktop Shortcuts

The installation of FactoryTalk Historian created a new Start menu program group. There are
several utilities in that group which will be used throughout this course. You may wish copy one
or more these shortcuts onto your desktop to provide easier access during the course.
IMPORTANT NOTE: Always Use Stop FT Historian system Shortcut

From this point on, you should always use the Stop FT Historian system shortcut
before you shutdown, restart, reboot, or even pause the VM-HIST-1 image. This will ensure
that all subsystems are shutdown cleanly, which may not always happen if you rely on them
automatically shutting down in response to an operating system shutdown request.
Rev. 121908
Page 28
Add data points to the local interface

a. If not already open, from the Start menu, open the FactoryTalk Administrator
Console
2. If just opening the FactoryTalk Administrator Console, do the following steps:

o Select the Network option
o Click OK
Rev. 121908
Page 29

Select the InstaCorp application
Right mouse click and select Add Individual Historian Points

Click Browse Tags
Rev. 121908
Page 30

Expand the InstaSoap folder and click on the Online folder
In the right pane select TI100
Click on the Add Tag(s) to List button
Click OK
Rev. 121908
Page 31

Click OK
Close the FT Administration console

Rev. 121908
Page 32

Check the VM-HIST-1 check box (if not already checked)

Rev. 121908
Page 33

Select the TI100 tag
Click OK

Verify that the TI100 tag has a value
Click the Start Updating button and verify value changes
Rev. 121908
Page 34


Rev. 121908
Page 35

Select the TI100 tag
Click OK


Close the SMT tool
Rev. 121908
Page 36
PART B - Install the Distributed Interface Node software

Because data buffering is only available on interfaces installed on computers other than the
historian server, we will install that FactoryTalk Live Data interface on the VM-DATA-1 image.
1. Verify that you are on the VM-DATA-1 image by checking for the following in the upperright corner:
3. Select the Install FactoryTalk Historian option:
Rev. 121908
Page 37
4. Click Next
Rev. 121908
Page 38
7. Proceed through the wizard and select the Historian Interface Installation
type:
Rev. 121908
Page 39
8. Verify that you selected the correct setup type by verifying the two entries in the New or
Upgraded Components list and then click Install: This will install all the components
Rev. 121908
Page 40

o DEelect Install FactoryTalk Activation
o Click Finish
Rev. 121908
Page 41
[Optional] Create VM-DATA-1 Desktop Shortcuts

The installation of the FactoryTalk Live Data interface created a new Start menu program
group. There are a couple utilities in that group which will be used throughout this course. You
may wish copy one or more these shortcuts onto your desktop to provide easier access during the
course.
Rev. 121908
Page 42
Register the FTLD Distributed Interface

Now that the distributed interface has been installed, we need to register these components with
the FactoryTalk Directory. In the first release of FactoryTalk Historian SE, this configuration
must be performed on the computer containing the historian server.
4. Right-click on the newly registered Production Historian and choose the New Data
Collection Interface option:
Rev. 121908
Page 43
5. Using the drop-down boxes, change the Computer hosting the interface to VM-DATA-1
and the Startup Type to Automatic, then click Apply.
Rev. 121908
Page 44
6. Use the Start button to start the remote data collection interface service. Click OK
when finished:
7. Verify that the FTLD2 interface is now displayed under the Production Historian:
Rev. 121908
Page 45
FT Historian Add Data Points

FactoryTalk Historian provides wizard which can interrogate FactoryTalk directory data sources
and configure their data points for collection.
image:
4. In the network tree, right-click on the InstaSoap area and choose the Add Individual
Rev. 121908
Page 46
5. Select the FLD2 data collection interface, then click the Browse Tags button.
Rev. 121908
Page 47

1. Expand the InstaSoap, Mixing and CLX1 folders and click on the Online folder
2. In the right pane select T100_Sim_Vol
3. Click on the Add Tag(s) to List button
4. Click OK
Rev. 121908
Page 48
7. Select OK on the following dialog:
Rev. 121908
Page 49

From the Start Menu select All Programs>Rockwell Software>FactoryTalk

Check the VM-HIST check box
Rev. 121908
Page 50


Select the T100_Sim_Vol tag
Click OK
Rev. 121908
Page 51

Verify that the T100_Sim_Vol tag has a value
Click Start Updating and verify value changes

Rev. 121908
Page 52


Select the T100_Sim_Vol tag
Click OK
Rev. 121908
Page 53


Close the SMT tool
Rev. 121908
Page 54
Install FT Historian Security Component

In order to use FactoryTalk Historian GUI utilities on the VM-DATA-1 image, we must install
some security components to support FactoryTalk Directory.
4. Select the Install FT Historian Security Component option:
Rev. 121908
Page 55
5. Click Next
6. Click Install
Rev. 121908
Page 56
Rev. 121908
7. Click Finish
Page 57
Add Historian Server Connection on Distributed Interface Node

We can use the FactoryTalk Administration Console to perform basic scan class configuration on
the remote interface. For more advanced configuration, we must use the System Management
Tools (SMT) and Interface Configuration Utility (ICU) installed locally on the VM-DATA-1
image. In order to use these tools, we must configure a connection to the Historian Server.
2. Launch the About PI-SDK utility:
Rev. 121908
Page 58
4. Choose Add Server from the Server menu:
Rev. 121908
Page 59
5. Input the Network Node of VM-HIST-1. Uncheck Confirm. Click OK:
6. We now want to remove the useless connection to VM-DATA-1 on which there is no

historian server. DO NOT click on the checkbox, click on the name VM-DATA-1 on the
server list:
Rev. 121908
Page 60
7. From the Server menu, choose Remove Selected Server:
8. Confirm the removal of the VM-DATA-1 connection by clicking Yes:
Rev. 121908
Page 61
9. Change the Connection Timeout to 30 seconds (for purpose of this class) and then
click the Save button:
10. Finally, click the VM-HIST-1 checkbox and verify connection:
11. Close the Connection Manager application and then close the About PI-SDK application.
Rev. 121908
Page 62
Enable Buffering on Distributed Interface Node

We are using a distributed interface node because buffering cannot be enabled on interface
located on the same computer as the FactoryTalk Historian server. We have not yet configured
the distributed interface node to use buffering, so up to this point we are still vulnerable to data
loss caused by network connectivity problems or a shutdown on the historian server. In this next
section, we will configure and enable buffering on VM-DATA-1.
2. Launch the System Management Tools (SMT):
Rev. 121908
Page 63
3. If not checked, click on the VM-HIST-1 checkbox in the upper-left corner and then Select
the Trusts plug-in under the Security category:
4. Click on the Trust_PIAPIBuffService trust and the click on the Copy Trust
toolbar button:
Rev. 121908
Page 64
5. Change the Trust Name to Trust_PISDKBuffService and the

Application Name to pibufss.exe then click the OK button:
6. You should now have one interface and two buffer trusts:
Rev. 121908
Page 65
7. Close the SMT and launch the Interface Configuration Utility:
8. From the interface combo box Select the FTLD2 (FTLData2) VM-HIST-1
Rev. 121908
Page 66
9. From the Tools menus, select Buffering
10. On the Choose Buffer Type section, click the radio button for Enable
buffering with PI Buffer Subsystem and click the Yes button on the
confirmation dialog:
Rev. 121908
Page 67
11. Wait until the status box shows Current Configuration: Good and then click on
the Buffered Servers configuration section:
12. In the Buffering to collective/server drop-down, select VM-HIST-1 and then click the
OK button:
Rev. 121908
Page 68
13. If asked Would you like PI-ICU to stop and restart PI Buffer Subsystem and all the
interfaces that are dependent on it?, click Yes.
14. Back in the main ICU dialog, click on the Service section:
15. If the interface starts before the buffering subsystem has started, data will be lost. To prevent
this, all interfaces on the buffered node should be made dependant on the buffer subsystem
service. Click Yes when the ICU offers to configure this for you:
Rev. 121908
Page 69
16. Restart the FTLD2 interface by clicking the Restart interface service toolbar
button:
17. When the status bar returns to Ready and Running close the SMT as configuration is
complete:
Rev. 121908
Page 70
Part C - Installing Visualization Applications

What You Will Learn
How to install components including:

FactoryTalk Historian DataLink
FactoryTalk Historian ProcessBook
FactoryTalk DataLink is a Microsoft Excel add-in that allows both historian configuration and
reporting. Microsoft Excel is already loaded on VM-HIST-1 so we only have to install
FactoryTalk DataLink and register the add-ins with Excel.
Rev. 121908
Page 71
4. Select the Install DataLink Client option:
5. Proceed through the wizard, choosing a Typical installation when appropriate:
Rev. 121908
Page 72
6. When the wizard is completed, launch Excel 2003:
7. From the menu, choose Tools - Add-Ins:
Rev. 121908
Page 73
8. Click on the Browse button:
9. Browse to the file:

Historian\Server\PIPC\SMT\PITagCnf.xla
Rev. 121908
Page 74
10. Click on the Browse button again and find the following file:
Historian\Server\PIPC\MDBBuilder\MDBBuilder.xla
11. Click on the Browse button a third time and find the following file:
Historian\Server\PIPC\Excel\pipc32.xll
Rev. 121908
Page 75
12. Click OK on the Add-Ins dialog box:
13. Click OK on any ActiveX warnings:
Rev. 121908
Page 76
14. The PI, PI-SMT, and PI-SMT - Module Database Builder menus should
now be available:
15. Close Microsoft Excel.
Rev. 121908
Page 77
Install FactoryTalk ProcessBook on VM-HIST-1

2. Run the setup.exe located in the FactoryTalk Historian SE_PB installation folder.
(Ask instructor for exact location)
3. Select the Install ProcessBook Client option:
Rev. 121908
Page 78
4. Proceed through the wizard and select a Typical setup type:
5. When the wizard finishes, reboot the image when prompted:
Rev. 121908
Page 79
[Optional] Create ProcessBook Desktop Shortcut on VM-HIST-1

Throughout the rest of this course we will often use the ProcessBook application. You may wish
to create a desktop icon shortcut for launching ProcessBook more easily.
If you wish to create the desktop icon, simply Ctrl-drag and drop the ProcessBook shortcut from
the Start menu onto the desktop:
Rev. 121908
Page 80
Rev. 121908
Appendix E
What You Will Learn
How to use the FactoryTalk Historian auto-discovery wizard

to locate and configure data points for collection.
In a ControlLogix processor that is running in the VM-CLX image, there are six tag structures
using a User-Defined Data type. These structures are as follows:
Each of these structures consists of several members. PV (process variable) is one of them:
FT Historian Auto discover of tags

FactoryTalk Historian provides an auto-discovery wizard which can interrogate FactoryTalk
directory data sources and automatically configure their data points for collection. In this
exercise we will use the wizards advanced rules definition to select a specific group of tags for
collection by the historian server.
image:
Rev. 121908
Appendix E Using Discover Historian Points (Version 2.0)
Page 2
9. In the network tree, right-click on the InstaSoap area and choose the Discover
Rev. 121908
Page 3
10. Begin by DEselecting the PLC-5, SLC-500, and MicroLogix Controllers

and Other OPC-DA Servers checkboxes. Next, change the data collection
interface to FTLD2. In our distributed configuration, there is no RSLinx Enterprise
on VM-HIST-1 so FTLD1 would not be able to collect the data. Also note that this
selection does NOT affect what data points will be identified for collection. It only specifies
which interface should actually attempt to collect the data. Finally, click the Edit
Discovery Rules button:
Rev. 121908
Page 4
11. Begin by DEselecting the Include default rule set checkbox. The default rule
set will select approximately 1300 tags in our SoftLogix program which is overkill for this
exercise. Next, click on the New button to create a new auto-discover rule. Set the rule to:
From Logix Controllers include tags where member is PV, add
points for .PV
Finally, click the OK and then the Save button:
12. Click on the Next > button to begin the discovery process:
Rev. 121908
Page 5
13. You will see this window while the discovery process is performed. Discovery can take
several minutes. You should not be alarmed if several minutes go by without any points
being added. We used a relatively narrow specification for discovery in this exercise:
14. When the discovery process is completed, you will be presented with a list of the matching
points. You have the opportunity to deselect individual or groups of points, change the scan
class for individual or groups of points, or even open a tag browser interface to add more
points. Click the Confirm Points button:
Rev. 121908
Page 6
15. The completion dialog confirms that 6 data points were added to the historian using interface
FTLD2. Remember that it may take up to two minutes for the interface is be notified and
begin collection of the new points. Click the OK button and then close the FactoryTalk
Administration Console:
Rev. 121908
Page 7


Check the VM-HIST-1 check box
Rev. 121908
Page 8


Select the Demo_Temp.PV tag
Click OK

Verify that the Demo_Temp.PV tag has a value
Rev. 121908
Page 9


Rev. 121908
Page 10

Select the Demo_Temp.PV tag
Click OK

Rev. 121908
Page 11

Close the SMT tool
The remainder of this lab will have you create a Trend in ProcessBook to test one of the
tags you created. You could also use System Management Tools (SMT) to view current or
recorded values for the tags.
12. Select the VM-HIST-1 Server by clicking OK

Rev. 121908
Page 12
18. Select new ProcessBook Display (.pdi) File, set the Display Name to Test, and click
the OK button:
Rev. 121908
Page 13
22. Click on the Tag Search button to select the following tag (refer to previous lessons for
detailed steps):
InstaCorp.InstaSoap.Soap Mixing.RSLinx Enterprise:CLX1.T100_Demo_Temp.PV
Set the Plot Time Start to *-10 Minutes. Click the OK button:
Rev. 121908
Page 14
23. Verify that the tag is recording data:
24. Close the ProcessBook application. This exercise is finished.
Rev. 121908

SW HOTT #1 Student Manual - 12-19-08

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SW HOTT #1 Student Manual - 12-19-08

Caricato da

Copyright:

Formati disponibili

STUDENT MANUAL FACTORYTALK HOTT #1

Contact Rockwell Automation

2008 Rockwell Automation, Inc. All rights reserved.

Installing FactoryTalk Historian (Version 2.1)

Using Discover Historian Points (Version 2.1)

Understanding Historian Tags and Using Excel Tag

Using Data Collection Modes of Polled vs. Advised

Buffering Distributed FTLD Interface Data

Understanding and Using Exception and

Configuring Performance Equations

Configuring Event Trigger Reads

Configuring Basic Output Points

Using Data Collection With Handshaking

Understanding and Using Basic Alarms

Configuring Event Framing-BaGen

Working with Digital States

Using FTLD Health Points

Using and Displaying Audit Information

Using Archive Management Tools

Scheduling Backups of Historian Data

Configuring Interface Redundancy

Using View SE Updated Trend Object to Display

2008 Rockwell Automation, Inc. All rights reserved.

Configuring and Using ProcessBook SQC

2008 Rockwell Automation, Inc. All rights reserved.

1. How to install the components of FactoryTalk Historian

Historians are utilized across many industries and applications:

2008 Rockwell Automation, Inc. All rights reserved.

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

2008 Rockwell Automation, Inc. All rights reserved.

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

FactoryTalk LiveData (FTLD): A direct data interface to FactoryTalk LiveData delivers

FactoryTalk Directory: FactoryTalk Historian uses FactoryTalk Directory to look up data

FactoryTalk Security: By integrating FactoryTalk Historian with FactoryTalk Security,

FactoryTalk Activation: FactoryTalk Historian is activated by Rockwell Automation's

FactoryTalk Diagnostics: Because of FactoryTalk Historian's close integration with

FactoryTalk View SE Trending: FactoryTalk View Supervisory Edition natively trends

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

Third-Party Historian Interfaces

2008 Rockwell Automation, Inc. All rights reserved.

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

9518-HINUNIFILE Historian Interface for Universal File Loader media only

FactoryTalk Historian ProcessBook Client License for View SE

2008 Rockwell Automation, Inc. All rights reserved.

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

FactoryTalk Historian Integration with FactoryTalk Batch

Windows 2000 Operating System

2008 Rockwell Automation, Inc. All rights reserved.

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

FactoryTalk Historian Site Edition 50,000 Points and Below

Minimum: Intel Pentium Xeon dual processor, 3.4Ghz, 4GB RAM

Minimum: Intel Celeron D, 3.0Ghz, 512MB RAM

Minimum: Intel Pentium III, 600MHz, 512MB RAM

2008 Rockwell Automation, Inc. All rights reserved.

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

FactoryTalk Historian Site Edition Network Client

Minimum: Intel Pentium III, 600Mhz, 512MB RAM

Choosing a Setup Type

2008 Rockwell Automation, Inc. All rights reserved.

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

2008 Rockwell Automation, Inc. All rights reserved.

Lesson 1 Installing FactoryTalk Historian (Version 2.1)

The Virtual Machines

2008 Rockwell Automation, Inc. All rights reserved.