FactoryTalk Historian Site Edition: Advanced Lab

For Classroom Use Only!

Important User Information

This documentation, whether, illustrative, printed, online or electronic (hereinafter Documentation) is intended for use only as a learning aid when using Rockwell Automation approved demonstration hardware, software and firmware. The Documentation should only be used as a learning tool by qualified professionals. The variety of uses for the hardware, software and firmware (hereinafter Products) described in this Documentation, mandates that those responsible for the application and use of those Products must satisfy themselves that all necessary steps have been taken to ensure that each application and actual use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards in addition to any applicable technical documents. In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter Rockwell Automation) be responsible or liable for any indirect or consequential damages resulting from the use or application of the Products described in this Documentation. Rockwell Automation does not assume responsibility or liability for damages of any kind based on the alleged use of, or reliance on, this Documentation. No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or software described in the Documentation. Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are responsible for:

properly using, calibrating, operating, monitoring and maintaining all Products consistent with all Rockwell Automation or third-party provided instructions, warnings, recommendations and documentation;

ensuring that only properly trained personnel use, operate and maintain the Products at all times; staying informed of all Product updates and alerts and implementing all updates and fixes; and all other factors affecting the Products that are outside of the direct control of Rockwell Automation.

Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell Automation is prohibited. Throughout this manual we use the following notes to make you aware of safety considerations:

Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

Identifies information that is critical for successful application and understanding of the product.

Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you: identify a hazard avoid a hazard recognize the consequence

Labels may be located on or inside the drive to alert people that dangerous voltage may be present.

Labels may be located on or inside the drive to alert people that surfaces may be dangerous temperatures.

3 of 136

FactoryTalk Historian Site Edition: Advanced Lab

Contents

Before you begin ........................................................................................................................................... 4

About this lab .................................................................................................................................................................................... 4

Tools & prerequisites ........................................................................................................................................................................ 4

Lab 1 - Understanding and Using Exception and Compression ................................................................... 6

Lab 2 - FactoryTalk Historian Tag Types .................................................................................................... 15

Lab 3 - Using Performance Equations and Totalizers ................................................................................ 22

Section 1 Performance Equations ............................................................................................................................................... 22

Section 2 - Totalizers ...................................................................................................................................................................... 32

Lab 4 FTLD Interface Buffering and Redundancy ................................................................................... 38

Section 1 - Interface Buffering ........................................................................................................................................................ 38

Section 2 - Interface Redundancy ................................................................................................................................................... 45

Lab 5 - Using and Displaying Audit Information .......................................................................................... 65

Lab 6 VantagePoint Dashboards with Historian Data .............................................................................. 74

Lab 7 - Accessing FactoryTalk Historian SE Data via OLEDB ................................................................... 91

Lab 8 - Configuring Event Framing and Using BatchView ........................................................................ 107

4 of 136

Before you begin

If not already done, the following steps must be completed before starting the lab exercise:

1. Set VMware images (DATA, SERVER and CLIENT) to Beginning of Lab snapshots.

2. Start the VMware images for the labfirst SERVER until fully running, then DATA until fully running and finally CLIENT until fully running.

About this lab Welcome to the FactoryTalk Historian Advanced Lab! This session provides you with an opportunity to explore more advanced features of FactoryTalk Historian Site Edition. The following sections explain what youll be doing in this lab session, and what you will need to do to complete the hands-on exercises.

FactoryTalk Historian Site Edition is a solution for optimizing your manufacturing process through the analysis of historical data. Historian provides the capability to collect, store, analyze, and visualize data using a powerful capturing engine and a powerful set of reporting tools such as time-series trends and easily generate reports using Microsoft Excel.

This lab is a pick and choose lab, with eight (8) different labs to choose from. Each lab will take about 30-45 minutes, so it is not expected that you will finish all eight labs. You will be able to download this manual after RSTechED, for further learning later.

Tools & prerequisites

Software

This hands-on lab uses the following software: Microsoft Windows Server 2008 R2 Standard SP1 Microsoft Windows 7 Enterprise SP1 Microsoft Internet Explorer, version 9 Microsoft Office Excel 2010 32-bit SP1 Microsoft SQL Server 2008 Standard Edition R2 FactoryTalk Historian Site Edition, version 3.01 FactoryTalk VantagePoint, version 4.5 FactoryTalk Historian ProcessBook, version 3.20.04 FactoryTalk Historian BatchView Add-in, version 3.1.2 FactoryTalk Services Platform, version CPR 9 SR 5.1 SoftLogix, version 20 RSLogix 5000, version 20 (CPR 9 SR 5) RSLinx Classic, version 2.59 (CPR 9 SR 5) RSLinx Enterprise, version 5.50 (CPR 9 SR 5.1) PI OLEDB, version 2010 R3

5 of 136

VantagePoint Dashboard Builder (Xcelsius 2008)

Image configurations/content

One (1) host computer with VMware virtualization software will host three guest operating systems for a total of three virtual computers in a workgroup. The VMware images are named and basic contents are as follows:

DATA: A Windows 2008 Server computer to act as a data collector using a FactoryTalk Live Data Interface. SERVER: A Windows 2008 Server computer to act as a FactoryTalk Directory and FactoryTalk Historian Site Edition

and VantagePoint Servers. Internet Information Server (IIS), Microsoft SQL Server 2008 Standard Edition have also been pre-installed. SoftLogix controllers and RSLinx Enterprise are on this image as well.

CLIENT: A Windows 7 Enterprise computer to act as a client for FactoryTalk Historian SE and VantagePoint.

Communications Overview:

Virtual Ethernet

SERVER (FTDirectory,

FTHistorian SE and FTVantagePoint

Servers, SoftLogix and RSLinx)

CLIENT (FTHistorian and

FTVantagePoint Clients)

Host PC

DATA (FactoryTalk Live Data

Interface)

6 of 136

Lab 1 - Understanding and Using Exception and Compression

In a FactoryTalk Historian system, data collected by a FactoryTalk Live Data Interface (values and timestamps) passes to the Server Snapshot. From there, data will pass to the Archives. Each tag has individual settings for Exception and Compression Deviation. Exception settings adjust how much filtering of data occurs between the Interface and the Snapshot. Compression settings adjust how much filtering of data occurs between the Snapshot and the Archives. By increasing or decreasing the Exception and Compressions settings, you can reduce or increase the amounts of data going to the Snapshot and the Archives.

7 of 136

Part A - Filter Less with Exception/Compression

1. Start on the Client image.

2. Start System Management Tools (SMT) by going to Start > All Programs > Rockwell Software > FactoryTalk Historian SE > System Management Tools.

3. Do these steps in this order: Select Points > Point Builder Search for and display the tag ending in *MachineStep (Click Tag Search button, specify *MachineStep in Tag Mask

field, click Search, select tag and click OK) Click on this tag in the upper pane to make sure it has focus Click the Archive tab

4. Note that this tag currently has default Exception and Compression attributes. Verify these attributes are currently set as follows: Exception Deviation: 0.25 Eng. Units Compressing: On Compression Deviation:0.5 Eng. Units

8 of 136

5. Do the following steps in this order: Select Data > Current Values Search for and display the tag ending in *MachineStep Click Start Updating

6. Verify that the value of this tag is incrementing from 0 to 5 (0, 1, 2, 3, 4, 5) over approximately a one minute period, then resetting to 0 and incrementing to 5 again, repeatedly. Watch at least one complete cycle.

7. Do the following steps in this order: Go to Data > Archive Editor Search for the tag that ends in *MachineStep Click Get events to get the last two hours of data in the archives for this tag. Note default Start time of *-2h (two hours

ago) and End time of * (now).

9 of 136

8. Scroll down the list of Value/Event Time entries. Are you seeing values for this tag of 0, 1, 2, 3, 4 and 5 over and over again? Or, are you seeing "filtered" data "skipping" some of the values such as in the below example, "filtered" by exception and compression? (skipping of values is what you should be seeing at this time).

9. This behavior is how this tag's values are archived when using "default" exception and compressions settings. For the purpose of this training, and a more realistic set of data for this step type of tag, we want to be sure that all changes in this tag's value are archived.

10. Go back to Point Builder for this tag and change attributes as follows: Exception Deviation: 0 Compression Deviation: 0 Compressing: Off

11. Click the Save icon and verify receiving "Successfully edited point..." message.

12. Wait two minutes (IMPORTANT!) to be sure the FactoryTalk Live Data (FTLD) Interface has enough time to put your changes in effect.

13. Did you wait two minutes?? If not, wait. If so, go back to Data > Archive Editor. Click the Get events button and scroll to the bottom of your Value - Event Time window. You should be seeing values archived no longer "skipping" or "filtering" data. Be sure to scroll to the bottomthe results we want to see will only be during the last few minutes, not during the majority of the two hours of data being shown. Your most recent data should appear as follows (so skipping of values):

14. Compare these values to the ones you had seen back in step 8. By adjusting the Exception and Compression settings you have significantly changed what values end up in the archives. Close the SMT.

10 of 136

Part B - Filter More with Exception/Compression

1. Start on the Client image.

2. Start System Management Tools by going to Start > All Programs > Rockwell Software > FactoryTalk Historian SE > System Management Tools.

3. Do the following steps in this order: Select Data > Current Values Search for and select the tag ending in *TempZone1 (Click Tag Search button, specify *TempZone1 in Tag Mask field,

click Search, select tag and click OK) Click Start Updating

4. Verify that this tag's value remains "static" (unchanging) for approximately 45 seconds, then changes rapidly for approximately 15 seconds. The value changes from between 65 to around 395 during this time period. This behavior should repeat relatively consistently, creating one minute "cycles".

5. In System Management Tools (SMT), do the following steps in this order: Go to Data > Archive Editor Search for the tag ending in *TempZone1 Change Start time to *-1m to get last one minute of data from archives Click Get events Note that in below graphic the window size is reduced so you don't see all values returned, but you should be getting

around 14-17 events every minute from the archive for this tag

11 of 136

6. Minimize the SMT and start VantagePoint Trend by going to Start > All Programs > Rockwell Software > FactoryTalk VantagePoint > Trend.

7. In the Model, navigate to System > Sources > FactoryTalk > localhost > Historians > Production Historian > Tags and double-click on or drag the tag ending in TempZone1 to the plot surface.

8. In the above Trend you should visually be seeing the behavior you noticed earlier, every 45 seconds the tag ranges between 65 and 395 over a 15 second period.

9. Minimize Trend and go back to the SMT.

10. Do the following steps in this order: Go to Points > Point Builder Search for the tag ending in TempZone1 Click on the Archive tab

12 of 136

11. Note that this tag is currently using default settings from when it was originally brought into Historian with the FactoryTalk Administration Console. Current settings should be: Exception Deviation: 0.25 Compression Deviation: 0.5

12. Change the settings to the following: Exception Deviation: 10 Compression Deviation: 20

13. Note that these settings are in no way "recommended" or necessarily "typical" settings to be used in any other case except for purposes of this training lab. Your settings should now appear as follows:

14. Click the Save button and look for "Successfully edited" message in the Session Record:

15. Wait for two minutes (IMPORTANT!) and then go to Data > Archive Editor in the SMT and click the Get events button. If you closed the SMT you will have to again search for the tag ending in *TempZone1. You should now be seeing only 9-11 events in a one minute period. Earlier you were getting 14-17 events.

16. Return to the VantagePoint Trend that you had minimized earlier and review how that previous trend appeared. Click the Refresh button and you should get an updated trend that looks similar to what you had seen before.

13 of 136

17. A key outcome of this lab is that you have seen that by increasing the amount of exception and compression you have cut the amount of data going into the Historian Archive significantly...from approximately 17 values every minute to only 11. And, the overall trend of the data looks similar. Less data stored with similar trend of data over time.

18. Be aware, however, that the amount of data being discarded in this case could be significant in some cases and care needs to be taken not to filter data with exception and compression "too much".

19. To better visualize the changes that have taken place, right-click on the Trend plot surface and select Properties > Trace:

20. Turn on Point markers and click OK.

14 of 136

21. See if you can find where the changes you made to your exception/compression took place (you may need to change the trend to Last 10 minutes). In the below example, you can see that soon before 1:16:39 PM on 8/6/2012 the changes took place, with less points being archived in the same amount of time. See especially how the filtering reduced the number of points archived during the "ramping down" of the value back to the minimum? Can you find this point in your data?

22. Use the SMT to set the attributes on the TempZone1 tag back to the following: Exception Deviation: 0.25 Compression Deviation: 0.5

23. Be sure to Save your changes.

24. Close the SMT and Trend applications (no need to save the trend).

15 of 136

Lab 2 - FactoryTalk Historian Tag Types

A FactoryTalk Historian Live Data (FTLD) Interface can be configured to work with four types of tags: Advised (the default) RSLinx Enterprise polls a tag at a Scan Class rate (default of 1 second). When the value of this

tag changes, RSLinx passes the value and timestamp on to the FTLD Interface. Polled RSLinx Enterprise polls a tag at the Scan Class rate. The FTLD Interface is polling RSLinx at the same rate

for tag values. Event A second trigger tag is monitored. This tag is monitored for a particular change, either Increment, Decrement,

Anychange or Nonzero. When this trigger happens, the Event tag is read by the Interface. Output A Source Tag is monitored, and when this tag changes the value of this tag is written to the Output Tag. This

is how FactoryTalk Historian could send data outside of itself, such as to a Controller or HMI.

Part A - Polled versus Advised Collection Modes

1. Start on the Client image.

2. Do the following steps in this order: Start System Management Tools from Start > All Programs > Rockwell Software > FactoryTalk Historian SE >

System Management Tools Go to Data > Archive Editor Search for and display the tag ending in *TempZone1 Click Get events to see the last 2 hours of archived data for this tag

16 of 136

3. This tag is remaining relatively "static" or unchanging for 30-45 seconds, and then is changing rapidly for about 15 seconds. Scroll through the list of Value/Timestamps and see if you can see a time where there is a "gap" in changing data. The largest gaps should be between when the tag was static at approximately 65 and jumped in value. In the below example, there is a 3 second "gap" followed by a 43 second "gap". Try to find similar gap(s) in your data.

4. The reason this tag is currently giving "gaps" in data is that the data is not changing at this time, or, if it is but only slightly, it is being filtered with exception and compression. There are applications where it might be required to archive data at some minimum time interval, whether or not it changes. A Tag Attribute called Exception Deviation Maximum Time (ExcMax) can be used as the first step to achieve this functionality. Do the following steps in this order: In System Management Tools, go to Points > Point Builder Search for the tag ending in *TempZone1 Go to the Archive Tab Change Compressing to Off Change Exception Deviation Max. Time to Minutes: 0 and Seconds: 10

17 of 136

5. Click Save icon and look for "Successfully edited point" message in the Sessions Record.

6. Go to the Classic Tab, and change Location3 (controls Tag Type) from a 1 (Advised Mode) to a 0 (Polled Mode).

7. Save your change. As Polled Mode, the FTLD Interface is asking RSLinx Enterprise for the value of the tag at the tag's Scan Rate. This is currently every one second, determined by the 1 in Location4 (controls Scan Class). The Interface then decides based on the Exception settings, including ExcMax, whether or not to send the value/timestamp to the Historian Server for possible archival (depending on Compression settings). When in Advised Mode, RSLinx Enterprise would never send the value to the Interface, "unless" it had changed since the last time it sent the value/timestamp. So, the Interface would never have a chance to send the value/timestamp to the server when it wasn't changing.

8. Wait two minutes (IMPORTANT!) to give the FTLD Interface time to see these tag edits. Go back to Data > Archive Editor and click Get Events.

9. Scroll down to the bottom of the data and look for value/timestamps such as the below. Even though the tag's value did not change, value/timestamps are archived at least every 10 seconds. Note that when a value "outside" the 10 second window is archived, the "previous value" is archived as well. That is why you should be seeing "pairs" of the same value in the archive, one second apart. The tag was being "polled" every second, and if it didn't change there was a value archived anyway from "outside" the 10 second window, and its previous value that would have been "inside" the 10 second window.

10. When done confirming/observing the above results, in Points > Point Builder change the attributes of the TempZone1 tag back to the following: Change Compressing to On Change ExcMax to Minutes: 10 and Seconds: 0 Location3 to a 1 Be sure to Save your changes

11. Close the SMT.

18 of 136

Part B - Event Tags

1. Start on the Client image.

2. Start the System Management Tools by going to Start > All Programs > Rockwell Software > FactoryTalk Historian SE > System Management Tools.

3. Do these steps in this order: Go to Data > Current Values Search for and select the tag ending in *Shift_Timer.ACC Click Start Updating Notice the value of this tag changing approximately every second

4. Do the following steps in this order: Select Points > Point Builder Search for and display tag ending in *Shift_Timer.ACC Click on Classic Tab

19 of 136

5. Location3 is currently set to 1 which is Advised Mode. Location4 is set to 1 which is identifying a 1 second Scan Class for this tag. Change Location3 to a 0 for Polled/Event collection mode.

6. If you save and "only" made the above change, the tag would be in Polled mode, with the Interface polling RSLinx Enterprise for the value of the tag every second. We actually want this tag to act in Event mode, updating when some "event" or "trigger" occurs. Do these steps in this order: Go to the General tab In the Exdesc field, enter the following (Note that "EVENT" must be uppercase!):

EVENT='RA Foods:RSLE:BL1.Program:Proof_Oven.SimpleMachineStep' Nonzero Note in the above there should be spaces between RA and Foods, and between MachineStep' and Nonzero. Click the Save icon and look for "Successfully edited point" message

7. Go back to Data > Current Values and add the *Proof_Oven.SimpleMachineStep tag to your display and click Start Updating. If it was left in the Start Updating mode, after you add this tag you may need to select Stop Updating and then Start Updating again. You should see that instead of every one second, the value of the Timer.ACC is now updating only when the MachineStep tag triggers the read, by changing to anything "except" a zero.

20 of 136

Part C - Output Tags

1. On the Client image, got to System Management Tools (should be open from previous steps).

2. Go to Points > Point Builder and add tag RA Foods:RSLE:BL1.StorageDint1 (be sure you click on to highlight this tag once you've added it to the tag list).

3. On the Classic Tab, change Location3 to a 2, in order to make this an Output Tag.

4. Back on the General Tab, use the Source tag Search button to select the *Shift_Timer.ACC tag.

5. Save your changes.

6. Go back to the Data > Current Values screen where you should be still seeing the value of this Shift_Timer.ACC tag along with the MachineStep tag.

7. To see the actual value of the *StorageDint1 output tag in the controller, start FactoryTalk Data Client by going to Start > All Programs > Rockwell Software > FactoryTalk Tools > Rockwell Software Data Client.

8. Select FactoryTalk and then Network directory.

9. Under $Global, select RA Foods and click OK.

10. Select OK to create Group1.

21 of 136

11. Select BL1 > Online, then StorageDint1 (dont pick StorageBool1 by accident!) and finally click OK.

12. Position Data Client over the top of System Management Tools (SMT) such as below. Note that when the value of the Shift_Timer.ACC changes (Source Tag), very soon after the StorageDint1 tag (Output Tag) is written to with the same value. This is how FactoryTalk Historian SE can write to a destination, in this case a SoftLogix controller tag.

13. When done verifying above, close the SMT and Data Test Client.

22 of 136

Lab 3 - Using Performance Equations and Totalizers

FactoryTalk Historian Servers include two key calculation capabilities: In addition to all the basic arithmetic operators, the Performance Equation 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.

The Totalizer subsystem performs common calculations such as totals, averages, minimum and maximum values, and standard deviations. Output of a calculation is stored in a Historian point.

Section 1 Performance Equations

Part A Simple Conversion Calculation

1. Verify that you are on the CLIENT image:

2. Launch the System Management Tools (SMT) by going to Start > All Programs > Rockwell Software > FactoryTalk Historian SE > System Management Tools.

3. Expand the Points category and select the Performance Equations plug-in. Then, click the New button.

23 of 136

4. Our first Performance Equation is going to be a Fahrenheit to Celsius conversion. On the General tab, do the following steps: Enter Name of TempZone1 Deg C Description of TempZone 1 Temperature converted to Celsius Point type of Float32 Eng Units of Deg C

5. Do the following steps: On the Equation tab, set the Equation to: ('RA Foods:RSLE:BL1.Program:Proof_Oven.SimpleTempZone1' - 32) * 5/9

(Hint: Use the Tag Search button to fill in the tag name) Click the Evaluate button just to make sure you dont get an error. If you do get an error, check your syntax carefully.

Your actual evaluated data value will likely differ from the 18.333 shown below:

6. On the Scheduling tab, do the following steps: Change the radio button to Event-based scheduling Use the Tag Search button to select the tag TempZone1 Change the timestamp assignment option to The timestamp of the triggering event

24 of 136

Tip - FactoryTalk Historian tag name length is typically limited to 256 characters. However, when a tag name is used with event-based scheduling with a Totalizer or Performance Equation, the event tags length cannot exceed 73 characters. This would be when used as part of an event expression in a Totalizer, or the Event tag in a Performance Equation.

7. On the Archive tab, set the following fields: Exception Deviation to 0 Compressing to Off

Tip - The above settings are totally dependent on the situation and may be different in real applications. In this case we are doing a calculation on a source tag that has already gone through exception and compression before going into the archive. This performance equation is doing a calculation based on that value and for purposes of this lab we want to archive all results. So, we are using zero exception and no compression.

8. Click the Save toolbar button and check for a success message in the session record:

25 of 136

9. Do the following steps in the SMT: Go to Data > Current Values Search for and display the two TempZone1 tags. You could use Tag Mask of *TempZone1* for this Search.) Select Start Updating You should see the TempZone 1 Deg C Performance Equation tag display calculated Celsius values from the source

TempZone1 tags Fahrenheit values

Part B Using a Performance Equation Function

1. Go back to Points > Performance Equations and click the New button.

26 of 136

2. Lets say we need to do maintenance on the Proof Oven when the temperature zones are so many minutes or hours over a certain temperature. In this case, as a starting point for such a set of calculations, we will create one Performance Equation to calculate the number of minutes TempZone1 is over 200 degrees in the last hour. First, do the following steps on the General tab: Specify name of TempZone1 GT 200 Descriptor of Minutes in last hour TempZone1 greater than 200 degrees Fahrenheit Point type Float32 Eng Units of Minutes

3. On the Equation tab, do the following steps: Enter following Equation (Hint: Use Tag Search button to fill in tag name rather than type in!):

TimeGT('RA Foods:RSLE:BL1.Program:Proof_Oven.SimpleTempZone1','*-1h','*',200) /60 Click Evaluate. You should be getting a value similar to the below and no errors

Tip - The TimeGT (time greater than) function includes the Tag Name, Starttime, Endtime and Value to be greater than in the parentheses that follow. The result is a value in seconds. In the above, we are dividing by 60 to convert seconds to minutes.

4. On the Scheduling tab, select Clock scheduling and Scan class of 3 which will cause the equation to be calculated every 30 seconds.

27 of 136

Tip - At this time the Scheduling tab is not identifying what actual time period the 3 in Scan class represents. Neither would it if you had entered a 1 or 2. You will do something later in this lab that will have an effect on this display.

5. On the Archive tab, set the following fields: Exception Deviation of 0 Compressing Off

6. Click the Save toolbar button and check for a success message in the session record.

7. In the top window, click on the TempZone1 GT 200 row to make sure it has focus.

8. Now, we want to open the Performance Equation Scheduling batch file to see where we could edit, add or delete scan classes if desired. Go to the SERVER Image.

28 of 136

9. Start the Interface Configuration Utility (ICU).

10. Click the Create New Interface Instance from .BAT file button.

11. Open the pipeschd.bat file located in C:\Program Files\Rockwell Software\FactoryTalk Historian\Server\bin.

29 of 136

12. As you can see, this interface is set at default to have three scan classes1, 2, and 3at 1 minute, 2 minutes and 30 seconds respectively.

13. Do not make any changes, but note the buttons above the scan class list that would allow you to add, delete and/or reorder the scan classes.

14. Close the ICU without having made any changes.

15. Go back to the CLIENT image that should still have the SMT open on the Performance Equations editor.

16. Close the SMT.

30 of 136

17. Reopen the SMT (closing and re-opening needed to see desired effect) and do the following steps: Go to Points > Performance Equations. Click Search (the binoculars icon) to list existing Performance Equation tags. Click on the TempZone1 GT 200 tag. On the Scheduling tab, note you now have a drop-down list box to select scan class and the time represented by this

scan class is shown. Compare to what you had seen previously in step 4.

Tip - This functionality exists because of what you did in the ICU on the Serveryou created the Performance Equation (PE) Scheduler Interface Instance. We could have done this before we created the Clock scheduled tag, but we wanted you to see the before and after. From now on, as you create additional PE tags, this functionality will continue.

31 of 136

18. Do the following steps: Go to Data > Current Values Search for and display tag TempZone1 GT 200 Click Start Updating You may see this tag occasionally changing by a small amount. Remember we are only calculating this Performance

Equation once every 30 seconds, and the oven temperatures are changing pretty consistently over time in our simulation.

19. Close the SMT.

32 of 136

Section 2 - Totalizers

Part A Summary Calculation Totalizer Example

1. Verify that you are on the CLIENT image.

2. Launch the System Management Tools (SMT).

3. Select Points > Totalizers and click the New button.

33 of 136

4. We will create a Totalizer to calculate the Moving Time Weighted Average of the Temperature of TempZone1. If there were multiple TempZones, this type of totalizing average temperatures could be used for determining maintenance needs, comparing efficiencies of different TempZones, etc. Start by doing the following steps on the Name & Type tab: Name of TempZone1 Average Temp Source tag of TempZone1 (see full tag name below) Summary calculation of Moving Time Weighted Average

5. On Sampling tab, specify Whenever a new source tag event occurs (Natural).

6. On the Results tab, do the following: Select Write final results After a time period elapses Results every 1 Minute Write interim results At source time (ramp)

34 of 136

7. On the Archive tab, do the following: Exception Deviation of 0 Compressing Off

8. Click Save and look for Successfully created totalizer message.

9. Do the following steps: Go to Data > Current Values Search for and monitor the tags TempZone1 and TempZone1 Average Temp Click Start Updating

Tip - For the first minute or so, the Totalizer tag might contain the text Pt Created or Configure. After this first minute (the first Write final results time period), the tag should start to update with interim values as new values are coming into the Source Tag. If more than a minute has gone by, and the Source Tag updates but the Totalizer remains Pt Created or Configure, there may be something wrong in its configuration (please check your previous steps).

35 of 136

Part B Count Events Totalizer Example

1. In the SMT, go to Points > Totalizers and click the New button.

2. On the Name & Type tab, enter the following: Name of BL1 Proof_Oven Machine Cycles Source Tag of MachineStep Count Events Events where value changes Block equal to 5 (we want the Totalizer we are creating to keep track of the number of cycles the Machine has gone

through, and we will consider reaching MachineStep 5 a cycle)

36 of 136

3. On the Results tab, verify/set the following: Start schedule at 0 Hour(s) after midnight Results every 1 Hour. Write interim results At source time (ramp).

Tip - These settings will cause the Totalizer to accumulate events every hour on the hour, write final results at the end of the hour, reset and start the count again. Write interim results set to At source time (ramp) will cause interim counts to be collected as they occur as well, the count not collected just at the end of each hour.

4. On Archive tab, set Exception Deviation to 0 and Compressing to Off.

5. Save the Totalizer and look for Successfully created totalizer message.

37 of 136

6. Add the Machine Cycles and MachineStep tags to Data > Current Values. Verify Start Updating is selected (may have to Stop and Start Updating again). You should see that every time the MachineStep reaches 5, the Machine Cycles tag increments. If the time on your image is nearing the start of a new hour (10am, 11am, 12pm, 1pm, etc), you should be able to see the Machine Cycles value reset. If not happening soon, perhaps you can come back later and watch it occur.

7. When ready to proceed, close the SMT.

38 of 136

Lab 4 FTLD Interface Buffering and Redundancy

Section 1 - Interface 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 (Pibufss), data flows from the data source, through the interface to the buffering service and from there to the Snapshot subsystem on the Historian Server.

1. Select the CLIENT image.

2. Launch VantagePoint Trend by going to Start > All Programs > Rockwell Software > FactoryTalk VantagePoint > Trend.

39 of 136

3. Go to System > Sources > FactoryTalk > localhost > Historians > Production Historian > Tags and click and drag the TempZone1 tag to the trend surface.

4. Click the Live Mode button and you should see the trend scrolling from right to left, continuously updating.

5. In order to monitor the buffering subsystem, there are queue statistics we can monitor on the computer with the Interface that is doing the buffering. The FTLD Interface FactoryTalk Historian Server is using is installed on the DATA image.

6. Switch to the DATA image.

40 of 136

7. Open the Interface Configuration Utility (ICU) from Start > All Programs > Rockwell Software > FactoryTalk Historian SE > Interface Configuration Utility.

8. From the drop-down Interface selection box, pick the FTLD1 interface.

9. Once selected, pick Tools > Buffering.

10. Notice that this interface is already configured to use the PI Buffer Subsystem.

11. Select Buffered Servers and notice this interface is configured to buffer data for the historian server we are using, named SERVER.

41 of 136

12. Click OK on the Buffering dialog and close the ICU.

13. Open a command prompt and change to the path of: C:\Program Files (x86)\Rockwell Software\FactoryTalk Historian\PIPC\BIN

14. Enter the command: pibufss qs.

Tip - pibufss is the buffer service, then there needs to be a space, a - (dash) followed by qs for queue statistics.

15. 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 (the interface currently has no need to buffer data).

16. Leave the Command Prompt open and return to the CLIENT image.

17. Verify that your VantagePoint Trend is still displayed and the TempZone1 tag is still changing.

18. Go to the SERVER image.

42 of 136

19. We will simulate a Historian Server outage by manually stopping Historian. Stop your Historian Server by selecting Start > All Programs > Rockwell Software > FactoryTalk Historian SE > Stop FactoryTalk Historian SE.

20. Wait for all of the services to stop and the dialog to close itself before proceeding (will take 1-2 minutes).

21. After Historian is fully stopped, go back to the CLIENT image and look at your VantagePoint Trend. When the Historian Server is shut down, you will see a break and apparent loss of data".

22. Go back to the DATA image.

43 of 136

23. Since the Historian Server is not available, the FTLD Interface is buffering data. You should see Current Queue Events accumulating (may take several updates).

24. Return to the SERVER image.

25. Restart the Historian Server by selecting Start > All Programs > Rockwell Software > FactoryTalk Historian SE > Start FactoryTalk Historian SE.

26. While the Server is restarting (may take several minutes), return to the DATA image.

27. See if you can catch when the server finishes restarting and the pibufss buffer empties. Current Queue Events value should go to 0 (zero) and the change since last value should be negative. Again, this may take several minutes.

28. One the buffer has emptied, return to the CLIENT image.

44 of 136

29. Your trend should now be updating with values.

30. If you see a gap, to fully refresh the trend, turn Live Mode off and back on again. The trend should be displaying data with no gaps.

31. Leave VantagePoint Trend open and in Live Mode for the next section of this lab.

32. Go to the DATA image. Make sure the command window has focus and select Ctrl-C to stop the queue statistics. Close the command window.

45 of 136

Section 2 - Interface Redundancy Interface-level failover allows you to install redundant copies of an interface on separate interface computers. This provides uninterrupted collection of process data even when one of the interfaces is unable to collect data for any reason. Interface node maintenancesuch as hardware upgrades, security updates, and software installscan occur without loss of data because the redundant node automatically collects and sends data to the Historian Server. Moreover, in the event of a hardware, network, or software fault, interface level failover prevents the loss of data, as the redundant node detects when the primary node fails and begins to send data to the Historian Server.

Tip - In the VMware images being used in this training, the FTLD Interface we have been using is on the DATA image. To demonstrate Interface Redundancy, another FTLD Interface has been installed on the CLIENT image. It is NOT recommended in real applications that Interfaces be run on client machines, but for the purposes of this lab we will use an interface on the CLIENT image as a redundant interface to the one on the DATA image.

Part A Configuring Buffering and Initial CLIENT Interface Configuration

1. Go to the DATA image.

2. Open the Interface Configuration Utility (ICU).

46 of 136

3. Use the ICU on this image to confirm the interface is running (select FTLD1 Interface from drop-down list and look for "Running" at the bottom of the dialog).

and configured for Buffering.

4. Close the Buffering dialog but leave the ICU open.

5. Go to the CLIENT image.

47 of 136

6. On the CLIENT image, we want to verify the connection to the Historian Server named SERVER. Launch the AboutPI-SDK utility.

7. Click on the Connections entry, the SERVER checkbox and confirm SERVER connected dialog appears at bottom.

48 of 136

8. Select File > Exit PISDKUtility to close the AboutPI-SDK.

9. Launch the Interface Configuration Utility (ICU).

10. Click the Create new Interface Instance from .BAT file toolbar button.

11. Navigate to the LDInterface directory and select the FTLDInt_FTLD.bat.bak file. Click the Open button.

49 of 136

12. You will be prompted to select the Host PI Server. Select SERVER from the drop-down box and click the OK button.

13. Note that the Interface ID is set to the default value of 1 and will be the same ID as that of our primary interface on DATA, Interface ID of 1.

14. Do the following steps: Select the Service category. Change the Display name to FTLD1. Click the service Create button.

50 of 136

15. Select Tools > Buffering.

16. Change the radio button to Enable buffering with PI Buffer Subsystem.

17. Read the messages and click OK (you will not start the service YET!).

18. You should be taken to the Buffered Servers dialog. Select SERVER from the drop-down box. Click the OK button.

51 of 136

19. First, click General and then click Service on the left. Click Yes make the PIBufss service a dependency. This dialog would come up later when you start the interface, but since we are finishing the configuration for Buffering we forced it to appear now to get out of the way.

20. One of the configurations of the Interface on the DATA image that was done in preparation for this lab was to delete some Scan Classes and enable Disconnected Startup. To make this interface match, first go to the General tab, click on them one at a time and use the Remove selected scan class button to delete scan classes 0.05, 0.1 and 0.25.

21. Your scan classes should now appear as follows.

52 of 136

22. Click on Disconnected Startup category and select Enable disconnected startup (with point caching).

23. Leave the ICU open.

Part B - Create Shared Folder

1. We need to create a shared folder to store a handshaking file that the two redundant interfaces will use to control their redundancy. Go to the SERVER image.

Tip - A computer running a Historian Server is NOT a recommended place for this shared "handshaking" folder. However, since it is the only image that will not be running an Interface, we will use it for training purposes in this lab.

2. Go to Start > Administrative Tools > Share and Storage Management.

3. Click on Provision Share on right side of dialog.

53 of 136

4. Click the Browse button.

5. Click the c$ drive and then Make New Folder button.

6. Name the folder FTH_Shared (press Enter after typing name) and then click OK.

54 of 136

7. Click Next > several times to accept defaults until this screen. Select the second option and then Next >.

Tip - In a real application, you may wish to adjust these permissions for a different user name or group of users.

8. Click Next > on dialog that follows and then Create on this dialog.

9. Click Close and then close the Share and Storage Management dialog.

55 of 136

Part C Configuring Interfaces for Failover

1. Change to the DATA image which should still have its ICU open.

2. Do the following steps: Select the Failover sub-category under UniInt in the left pane. Check the box to Enable UniInt Failover. Select Phase 2. For Synchronization File Path, browse to the FTH_Shared folder on Server (Network > SERVER > FTH_Shared)

and click Open. The file FTLDInt_FTLD_1.dat will be created in this folder. Select UFO (Universal FailOver) Type of HOT. Carefully confirm all following selections. When confirmed (are you sure?), select Apply.

3. Read this message (we will come back later to finish the configuration) and click OK.

56 of 136

4. Read and click OK (we will stop and restart the interface later).

5. Go to the CLIENT image.

6. Make the same Failover selections on this interface as you did on the other. HOWEVER - Select Failover ID # 2 for this instance and Failover ID # 1 for the other instance - IMPORTANT! Verify all below selections CAREFULLY!

7. Are you sure the settings match especially Failover ID# for this instance of 2 and other instance of 1? If so, click Apply on above dialog.

8. Read and click OK.

57 of 136

Part D Modifying FTLD Service Properties

1. Still on the CLIENT image, go to Services by selecting Start > Control Panel > System and Security > Administrative Tools > Services.

2. Double-click the FTLD1 Service.

3. Select the Log On tab, and specify to use Administrator account with password of rockwell. Click OK.

4. Read and click OK.

58 of 136

5. Close Services, Administrative Tools and System and Security dialogs.

6. Go to the DATA image.

7. Go to Services (Start > Administrative Tools > Services) and make the same changes to the FTLD1 interface service on this image. Use Administrator with password of rockwell. Click OK.

8. Read and click OK.

9. Read and click OK. You will not stop and restart the service YET!

10. Close the Services dialog.

59 of 136

Part E Finishing up and Testing the Interface Redundancy

1. Go to the DATA image (should already be on from last part of lab).

2. In the ICU, click the Browse button to select the other instance.

3. Click the FTLDInt1 interface on the CLIENT image and click OK.

4. In the tag area, below where you identified the UFO Type and Synchronization File Path, right-click on the tags and select Create UFO_State Digital Set on Server SERVER:

60 of 136

5. Read and click OK on this dialog.

6. Right-click on the tag area again and select Create all points (UFO Phase 2).

7. Click the Apply button at the bottom-right of the dialog box and click OK on the Interface Changes Require Restart dialog box that will appear.

8. Restart the interface. Look for Stopping Service, then Starting Service and then Ready and Running at the bottom-left of the dialog box. Leave the ICU open.

9. Return to the CLIENT image.

10. Select the Browse button.

61 of 136

11. Click the interface on DATA image and click OK.

12. Click the Apply button at the bottom of the dialog box and then start this interface by clicking Start Interface service.

13. Click Yes if asked if you would like the ICU to start the PIBufss Service.

14. Switch over to the SERVER image.

62 of 136

15. Launch the System Management Tools (SMT).

16. Expand the Data category and select the Current Values plug-in.

17. Use the search button to add all of the FTLDInt1_* tags to the current values monitor and click the Start Updating toolbar button.

You should be seeing: ActiveID = 1 or 2 Failover ID# of whichever Interface Node is currently "Primary" and sending data to Historian Server DeviceStatus = 0 Zero is good status Heartbeats = Incrementing numbers indicate Interface Nodes with Failover IDs #1 and #2 are responsive States = Current Primary or Backup state of Interface Nodes, Failover IDs #1 and #2. Under certain conditions could

also indicate Off or Transition

63 of 136

18. Leaving the SMT open, go to the CLIENT image and the VantagePoint Trend application, which should still be running from the previous lab. You may see a gap or temporary loss of data from interface configuration changes and restarts. If not running, start VantagePoint Trend and create a display with a trend of the tag ending in TempZone1.

19. On whichever of your images currently has the Primary interface, use the ICU to stop the Interface by clicking Stop interface service.

20. On the CLIENT image, there could be a short delay but then the backup interface should take over. You may need to stop and start Live Mode, but data collection will continue and no data should be lost.

64 of 136

21. Start the Interface again that you stopped earlier.

22. Switch back to the SERVER image.

23. Did the Interfaces switch roles? The Interface that was previously Backup is now Primary and the Interface that was Primary is now Backup?

24. Experiment with stopping a Primary interface to verify the Secondary Interface takes over, with no data loss. Just be sure you dont end up with both Interfaces stopped. You WILL FOR SURE lose data then!

25. When you are finished experimenting, revert back to non-redundant conditions by: Make sure the Interface Node on DATA (ID#1) is Primary On the CLIENT image, stop the Interface (if still running) with the ICU, then close the ICU. Use the ICU on DATA image to de-select Enable UniInt Failover, click Apply and Restart the Interface Node.

26. On all three images, close any open applications (SMT, VantagePoint Trend, ICU, etc).

65 of 136

Lab 5 - Using and Displaying Audit Information

The Historian Audit Database records the data that is added, edited, or removed from specific Historian Server database files, as well as other events or changes to configuration that occur in the Historian Server.

In addition to methods described in the Auditing the FactoryTalk Historian SE Server Users Guide you can use to store, export, and review audit records, Rockwell Automation provides the Historian AuditViewer utility, which enables you to view and manage Audit Database records. Historian AuditViewer is available as a separate package with its own documentation.

Tip - This lesson uses AuditViewer to display audit information. This tool is not installed automatically, but included in Redist/AuditViewer in Historian 3.x install media and/or downloaded from Knowledgebase article 64384 - FactoryTalk Historian Site Edition AuditViewer and has already been installed on the SERVER image.

Part A - Enable Auditing of your PI Server

1. Go to the SERVER image:

2. Launch the System Management Tools (SMT).

66 of 136

3. Do the following steps: Expand the Operations category and select Tuning Parameters. Click the EnableAudit Tuning Parameter.

Tip - The Auditing Mask entered value is a bit mask where each bit refers to a specific database. -1 enables 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, Server:16384, Collective:32768, Identity:65536, Identity Mapping:131072, Snapshot:268435456, Archive:536870912, DBsecurity:1073741824)

Value units are in bitmask. Parameter takes effect at startup only.

67 of 136

4. Double-click on EnableAudit to display the properties window. Change the auditing Value to -1 and click OK.

5. Close the SMT.

6. For the auditing entered value to take effect, FactoryTalk Historian must be stopped and restarted. Select Start > All Programs > Rockwell Software > FactoryTalk Historian SE > Stop FactoryTalk Historian SE. Wait for all services to stop and window to close.

68 of 136

7. Once all of the services have stopped and window has closed, select Start > All Programs > Rockwell Software > FactoryTalk Historian SE > Start FactoryTalk Historian SE. Wait for all services to start and window to close.

Part B - Make Changes and Use Audit Viewer 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 in the archive and also edit an attribute of a tag and view the change in the FactoryTalk Historian AuditViewer.

1. Open the SMT, expand the Data category and select Archive Editor.

2. From the archive editor, you need to search/select the tag value you wish to view/modify. Use the search button to select the tag BA:TEMP.1. The archive editor will display data for the time period specified in the lower window. Note you are displaying the last two hours of values in the archive at default (Start Time of *-2h and End Time of *).

69 of 136

3. Scroll down part-way through the data so that you are not looking at the beginning of the last two hours of data. Otherwise, when you later look for your edits you might have to look further back than the last two hours you are currently displaying. From the archive editor select the value you want to change and note its date/timestamp (write it down). Type a new value (modified value of 99 in below example), press Enter, then click the Save icon . The modified value will be displayed and marked as substituted (scroll to your date/timestamp and look for checkmark in Substituted column after these steps).

70 of 136

4. Do the following steps: Go to Points > Point Builder Search for tag BA:LEVEL.1 Go to Archive Tab Change Span to 101

5. Save changes by clicking the Save icon and look for success message:

6. From the SMT Tools menu select Audit Viewer to launch the application.

71 of 136

7. From the AuditViewer expand the Manage section. Verify the Archive 0 checkbox is checked (if not, check it) and then click the Manage link.

8. Double-click the Archive 0 icon on the right to display the subsystems file details.

9. 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. Do all three (only two shown below).

72 of 136

10. Confirm that the records are updated with current date/time (will not match below).

11. You can also view this in table form. Above the three Subsystems listed select the Table tab.

73 of 136

12. Change the search Start Time to past 5 minutes by specifying *-5m.

13. Select Search to display and audit records for the time period specified.

Tip - If you don't see records, perhaps more than 5 minutes have gone by since your changes. Try Start Time of *-10m in that case.

14. To view more detailed information, click the + symbols on the entries. This will display detailed information about the tag attribute old and new value, modified archived values, etc. Notice there are two tabs, for Configuration versus Timeseries entries. You should see entries such as: Configuration (Base) tab:

Timeseries (Snapshot/Archive) tab:

15. As time allows, make other FactoryTalk Historian edits/changes and detect them with Audit Viewer.

16. Close Audit Viewer and the SMT.

74 of 136

Lab 6 VantagePoint Dashboards with Historian Data

VantagePoint EMI includes a 30-day trial of Dashboard Builder. Dashboards can include a wide variety of graphics and capabilities to your VantagePoint EMI reporting system

Part A - Creating a Dashboard Report from a Template

1. Go to the CLIENT Image.

2. Start Xcelcius 2008 from the desktop icon or Start > All Programs > Xcelsius > Xcelsius 2008.

3. Click Continue when prompted.

4. Wait until all of the Xcelsius windows open, including an instance of Microsoft Excel in the lower-center of the screen.

5. We will use a partially completed template and add functionality to connect to Historian tags via VantagePoint. In the Xcelsius menu at the top of the screen, select File > Open and open:

C:\Class Files\Dashboard Template.xlf.

6. In the Microsoft Excel window in the middle of the screen, click on cell C3 (red cell). Select VantagePoint tab, Insert button.

75 of 136

7. Select History and click Next (Next button is not shown below).

8. In the VantagePoint Model, navigate to System > Sources > FactoryTalk > localhost > Historians > Production Historian and click on Tags. Select the TempZone1 tag and move it to the right with the > button. Click Next.

76 of 136

9. Select Use this Range and then click New.

10. Browse to MyEnterprise > Samples v4 > Support > Report Library > Time Periods, select the Last 1 minute time period and move it to the right with the > button. Click Next (not shown).

11. Be sure the Skip advanced options is NOT selected or unchecked, and click Next.

77 of 136

12. Select Average and number of samples of 1. Click Finish (not shown) and wait for the spreadsheet to populate with data.

13. Click on cell C12 (green cell).

14. Select the VantagePoint tab > Insert function again. Select History and after clicking Next you will see this screen. We are using the same tag, so just click Next.

78 of 136

15. We are using the same time range, so select Use this Range and click Next.

16. Do NOT select Skip advanced options and click Next.

17. This time click the Count option, number of samples at 1 and then Finish.

18. On the canvas area, click on Label 1.

79 of 136

19. On the right side of the screen in the General area (may need to click on it to give it focus), click the Link to Cell option and click the cell picker button (may need to widen this window for the "cell picker" to appear).

20. Select cell D6 and click OK.

80 of 136

21. Select Gauge1. On the right of the screen click the General area. Specify the Title to be Average Temperature. Browse to select Data By Range from cell D9 and set Maximum limit to 400.

81 of 136

22. Also on Gauge1, go to Appearance > Text tab and click on Value (make sure it remains "checked"). Below in the Number Format area, change to Numeric and select 2 Decimal Places.

82 of 136

23. Select Gauge2 on the canvas in the center of the screen. On the right, in the General area, specify the Title to be Number of Values and browse to set Data By Range to cell D18 and change Maximum Limit to 1000.

24. Resize your objects as desired and add color or other options of your choice.

83 of 136

25. Select View > Canvas Sizing > Fit Canvas to Components.

26. From the Data menu in Xcelsius (not the Excel menu) select Connections

27. Click Add and then Excel XML Maps.

84 of 136

28. Click Add and then Flash Variables.

29. Click Connection 1 Flash Variables.

30. Click Import Named Ranges. Items will be added.

85 of 136

31. Click the first ExcelXML Map.

32. Select the Usage tab. Turn on Refresh Before Components Are Loaded and Refresh every 30 seconds.

33. On the Definition tab, select the cell picker button.

34. Select cell C3 (red cell) and click OK.

86 of 136

35. Select the second ExcelXML Map and set the Usage tab as follows.

36. On the Definition tab, use the cell picker button and select cell C12 (green cell).

37. Close the Data Manager dialog.

38. Select File > Save As on the Xcelsius menu and save your dashboard as C:\Class Files\MyTemperatureReport.xlf.

87 of 136

39. Select File > Export > Flash (SWF)

40. Save to C:\Class Files directory as MyTemperatureReport.swf.

Tip - You will see the following dialog while the SWF file is being generated.

88 of 136

Part B - Publish and View the Dashboard from the VantagePoint Portal

1. From the Excel VantagePoint ribbon bar, Publish.

2. Use the icons to browse to the SWF and XLF files. Click Next.

3. Check the TimePeriods box to allow users change the TimePeriod as a Parameter in the report (you will see what this means when you view your report). Click Next (not shown).

89 of 136

4. Browse to the Reports folder under MyEnterprise > MyPlant and name the report MyTemperatureReport. Click Next (not shown).

5. Check the box for Browse to published dashboard and click Finish (not shown).

6. The report should soon appear, similar to the following. Approximately every 30 seconds you should see the two values update.

90 of 136

7. Note that you can select a different relative time period and click Generate Report and the gauges will reflect that average and count.

8. Note that you can select any Absolute Time Period and the report will reflect your choice when you click Generate Report.

9. Close VantagePoint Portal and Xcelsius.

91 of 136

Lab 7 - Accessing FactoryTalk Historian SE Data via OLEDB

In this lab, you will examine some of the built-in capabilities of the FactoryTalk Historian OLEDB layer. The OLEDB layer provides convenient access to archive data. You will also learn how to use the PI-OLEDB Tester to examine some sophisticated functionality provided by the OLEDB layer.

Tip - OLEDB Provider is a feature available in the Advanced Server option of FactoryTalk Historian SE and is already installed on your SERVER image.

References:

PI OLEDB exposes PI data in form of tables which are grouped into catalogs as listed below: piarchive contains archive related tables pibatch contains batch data tables pids contains PI digital state tables pifunction contains tables representing PE functions piheading contains heading tables pilog contains the pimessagelog table pimodule contains a set of tables representing the Module Database pipoint contains tag configuration tables (one per point class) piuser contains user database tables

Part A FactoryTalk Historian OLEDB Basics

1. Go to the SERVER image.

2. Launch the PI-OLEDB tester application by starting the following executable C:\Program Files (x86)\Rockwell Software\FactoryTalk Historian\PIPC\OLEDB\Tools\PI OLEDB Tester\PIOLEDBTester.exe

3. If prompted to login, select the Use Windows NT Integrated security checkbox and then click OK.

92 of 136

4. Select Sample Statements >>.

5. In the Archive Statements category, there are 34 sample queries. To help understand the statement functionality, each statement is accompanied with a short comment. Review entries to see how to handle the following types of situations:

Translating a digital state or status Retrieve snapshot data Count archive entries Work with annotations Work with timestep interpolated data Use SQL CASE statement

6. Click on various Sample SQL Statements and click Execute. Review results displayed at the bottom of the dialog.

7. If you like you can try editing one of the SQL Statements or try entering one of your own, executing and reviewing results.

8. Close PI-OLEDB Tester and any open dialogs or windows.

93 of 136

Part B - Using Microsoft Reporting Services

SQL Server 2008 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.

One of the sources of data that Reporting Services can work with is OLEDB Providers. The PI OLEDB is pre-installed on the SERVER image.

1. Verify that you are on the SERVER image.

2. From the Start Menu, launch the SQL Server Business Intelligence Development Studio by selecting Start > All Programs > Microsoft SQL Server 2008 R2 > SQL Server Business Intelligence Development Studio.

3. Once open, on the File menu, point to New, and then click Project

94 of 136

4. In the Project types list, click Business Intelligence Projects (see below graphic).

5. In the Templates list, click Report Server Project.

6. In the Name field, enter FTH MSReport.

7. Click OK to create the project.

8. The FTH MSReport solution will be displayed momentarily in Visual Studio (VS) Solution Explorer view (a window on the right side).

9. You need to specify the target Server URL for the project. In the Solution Explorer, right-click FTH MSReport and click Properties.

95 of 136

10. Set the Target Server URL to http://localhost/ReportServer (see below).

11. Click OK.

Tip - In order to collect data from the Historian server, you need to create a connection to the Historian server. In this lab, you will add a shared data source via PI OLEDB.

12. Right-click the Shared Data Sources folder and select Add New Data Source.

96 of 136

13. The Shared Data Source dialog box appears.

14. Enter PIOLEDB in the Name field.

15. Select OLE DB from the Type: drop-down list.

16. Click the Edit button to fill in the PI OLEDB connection properties (you will do in following steps).

17. Select OLE Provider to PI OLE DB Provider from the drop-down list.

18. Enter SERVER into Server or file name field.

19. Specify Use Windows NT Integrated Security.

20. Verify that the following options are selected and entered correctly in the image below.

97 of 136

21. Click Test Connection.

22. Verify that the connection succeeded and click OK, and OK again.

23. Add the following to the Connection string: ;Integrated Security = SSPI

24. Verify the above configuration options and click OK.

25. After the data source is defined, Report Designer creates a dataset (you named it PIOLEDB).

26. To create a report definition file, in the Solution Explorer right-click Reports, point to Add, and click New Item...

98 of 136

27. Select Report Wizard.

28. In Name field, leave the default name Report1.rdl.

29. Click Add.

30. The Report Wizard welcome page will be displayed. Click Next.

99 of 136

31. Verify the shared data source is set to PIOLEDB.

32. Click Next.

33. In the design query type the following: SELECT tag, time, value, status

FROM piarchive..picomp

WHERE tag LIKE ? AND time >= ? AND time

100 of 136

36. Click Next.

37. In the report design table, select tag and then click the Page > button to move tag into the page display field.

38. Select time and click Group > to move time into the Group display field.

39. Select Value and Status and click Details > to move value and status into the details display field.

40. Verify that the following groups have been configured.

41. Click Next.

42. Select the default Stepped.

43. Click Next.

44. Select the default Slate.

101 of 136

45. Click Next.

46. In Report Name field, leave the default report name Report1.

47. Click Finish.

48. A view opens that contains Design and Preview tabs; the report opens in Design view (may need to click on Design to give it focus).

102 of 136

49. From the Report Data window on the left, double-click on Parameter1.

50. Configure the Parameter1 properties with the following settings: Prompt: Tag Mask Data type: Text Click OK

51. Repeat the parameter configuration steps for Parameter2 with the following settings: Prompt: Start Time Data type: Date/Time

52. Repeat the parameter configuration steps for Parameter3 with the following settings: Prompt: End Time Data type: Date/Time

103 of 136

53. From the Visual Studio design view window select the Preview tab to preview Report1.

54. Set the parameters to the following: Tag Mask: *TempZone1 Start Time: Date and Time of 5 minutes ago (for example, 9/24/2012 6:01:00 PM) End Time: Date of tomorrow

55. Click View Report and observe the results.

56. In the Solution Explorer on the right side of Visual Studio, right-click on FTH MSReport and select Deploy.

57. Lower-left corner of Visual Studio should say Deploy startedand then watch for succeeded messages.

104 of 136

58. Right-click on the Report1.rdl report and select Deploy.

59. Watch for succeeded messages.

60. Close Visual Studio.

61. Start Internet Explorer by going to Start > All Programs > Internet Explorer.

105 of 136

62. Type in address of http://server/Reports

63. Click FTH MSReport.

64. Click Report1.

106 of 136

65. Set the parameters to the following: Tag Mask: *TempZone1 Start Time: Date and Time of 5 minutes ago (for example, 9/24/2012 6:01:00 PM) End Time: Date of tomorrow Click View Report

66. Enjoy your Internet Explorer report based on FactoryTalk Historian data!!

67. Close Internet Explorer.

107 of 136

Lab 8 - Configuring Event Framing and Using BatchView

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.

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.

108 of 136

Part A MDB to AF Preparation Wizard

The Module Database (MDB) Editor is a tool for working with the content in the Module Database on a FactoryTalk Historian Server. Each Historian Server includes a PI Module Database (MDB). The MDB stores information in a hierarchy that you can use to organize and classify resources according to your organization's needs. For example, you can store and view equipment type, office location, buildings names, and so on. You can also use the Module Database as a central registry for several Historian applications' settings, including ACE, ICU and BatchView.

Future development plans are to replace MDB with Asset Framework (AF). Over time, MDB applications will be transitioned to be AF applications. New client applications will support AF only. In order to provide backward compatibility, the current product migrates everything in the Module Database to AF and then keeps the objects synchronized. This allows MDB-based clients to access the objects through MDB and AF clients to access the same objects through AF.

Note that some key functionality of MDB and AF is modeling of equipment, machines, assets, etc. Rockwell Automation recommends using FactoryTalk VantagePoint for this type of modeling and asset organization.

1. Verify that you are on the SERVER image:

2. Select Start > All Programs > Rockwell Software > FactoryTalk Historian SE > MDB to AF Preparation Wizard.

109 of 136

3. Read the Welcome dialog and click Next.

4. Do the following steps: Click Analyze. Verify no issues found message appears. Click Next (Next button not shown below).

5. Click the AF Server Connect button.

110 of 136

6. Click the AF Database Browse button.

7. Click New Database.

8. Accept default name of Database1 and click OK.

111 of 136

9. First, click on the Database1 row to highlight (select), then click OK.

10. Click Next.

11. Read this message and click Yes.

12. Click Finish on below dialog and Congratulations!

112 of 136

13. Stop Historian by selecting Start > All Programs > Rockwell Software > FactoryTalk Historian SE > Stop FactoryTalk Historian SE.

14. Wait patiently for all services to stop and command prompt to close.

15. Only after all services have stopped and dialog closes, select Start FactoryTalk Historian SE.

113 of 136

16. Only after all services have started and command prompt closes, start the SMT.

17. Go to Operation > MDB to AF Synchronization and verify green (good) indicator and Current Status of InSync.

18. Close the SMT.

114 of 136

Part B - Configuring PIBaGen

1. Verify that you are on the SERVER image.

2. Launch the Interface Configuration Utility (ICU).

3. Click the Create new Interface from .BAT file toolbar button.

4. Navigate to the PIBaGen subdirectory location: C:\Program Files (x86)\Rockwell Software\FactoryTalk Historian\PIPC\Interfaces\PIBaGen (be sure you are in (x86) version of Program Files!).

5. Open the file named PIBaGen.bat.

115 of 136

6. The Interface will be named: PIBaGen.

7. Change the type from none to other_non_uniint.

8. From the ICU toolbar click Save.

9. Click Yes to continue when warned that no point source has been specified.

116 of 136

10. In the Service area, set Startup Type to Auto and click the Apply button. Click Yes if you get the message Do you wish to proceed without specifying a Point Source?

11. Click the Start button on the toolbar. Click Yes if asked Do you wish to proceed with interface startup without defining scan classes?

12. Go to Start > Administrative Tools > Services and check that the newly created PIBaGen service is Started (look for PI Batch Generator Interface).

13. Close the Services dialog and close the ICU.

117 of 136

14. Use Windows Explorer to navigate to the directory C:\Program Files\Rockwell Software\FactoryTalk Historian\Server\adm. Look closely for these three files which you will edit in the following steps. pisitestart.bat pisrvsitestart.bat pisrvsitestop.bat

15. Right-click on pisitestart.bat and select Edit from the context menu.

16. Remove the rem statements from in front of the PI-Batch Generator Interface block (7 total lines near the bottom of this bat file need to scroll down).

17. Save the file and Close Notepad.

18. Right-click on pisrvsitestart.bat and select Edit from the context menu.

19. Remove the rem statement from in front of net start pibagen.

118 of 136

20. Save the file and Close Notepad.

21. Right-click on pisrvsitestop.bat and select Edit from the context menu.

22. Remove the REM statement from in front of net stop pibagen.

23. Save and Close Notepad.

24. Close Windows Explorer.

Part C - Create a new PIUnit

1. Still on the SERVER image, launch the System Management Tools (SMT).

119 of 136

2. Do the following steps: Expand the Operation category and select Module Database. Under SERVER, right-click on Modules and select New

3. Name the Module BL1 (for Bread Line 1) and click OK (not shown).

4. Right-click on BL1 module and select New > PIUnit.

5. Enter Proof_Oven into the Module Name field and click OK (not shown).

120 of 136

6. Assign an alias to the Proof_Oven PIUnitright-click on Proof_Oven and create a new Alias.

7. Enter TempZone1 into the Alias Name field and map it to the PI Server named SERVER and tag ending in TempZone1 (use the Search button), and click OK.

8. Your Module Database should appear as follows:

Tip - In the Module Database you have now created a structure to represent our application of a BreadLine 1 with a Proof_Oven and a temperature of TempZone1 to be monitored. We are working towards keeping track of Events where batches of product enter the Proof_Oven and the temperature of TempZone1 is kept track of for each event or batch of product. Next, you will add a tag to Historian in order to keep track of the event name, start and stop times.

9. Launch the FactoryTalk Administration Console (Start > All Programs > Rockwell Software > FactoryTalk Administration Console).

10. Click Network directory and OK.

121 of 136

11. In the FactoryTalk Administration Console, right-click RA Foods and click Add Individual Historian Points

12. Select Browse Tags

122 of 136

13. Do the following steps: Browse RA Foods > BL1 > Online > Program:Proof_Oven > SimpleBatchID (full path or tree not able to be shown

below) Select the tag SimpleBatchID on the right Click Add Tags(s) to List and the selected tag will be displayed in the lower window Click OK

14. When you click OK on the above dialog, your screen should have the tag listed such as follows. Click OK on this dialog (OK button not shown).

15. Close Administration Console and switch back to System Management Tools (SMT).

123 of 136

16. Do the following steps: Expand the Batch category and select Batch Generator. Select SERVER in the middle pane under Registered Units Only tab (see below graphic). Select the Interface tab in the right pane. Set the Configuration Module Name to PIBaGen. In the middle pane, click the Save toolbar button.

17. Switch to the MDB View tab and click on the Proof_Oven PIUnit (SERVER > BL1 section).

124 of 136

18. Using Batch Generator, the right hand configuration view, select the PIUnitBatches tab and configure the following: Set the Active Point to use the SimpleBatchID tag (use Browse button). ActivePoint Behavior of Pulse. Strings indicating zeroth state of NOBATCHACT. Set Unit Batch ID Point to use the same SimpleBatchID tag. Change the Recovery Option to Do not recover anything.

Tip - In the simulation running in the SoftLogix controller, a new BatchID is being created at the start of every cycle of machine steps. The machine steps increment 0, 1, 2, 3, 4 and 5, then reset to zero and start over again. When reset to zero, the BatchID value goes to NOBATCHACT until incrementing to step 1. In the above dialog, the BatchID being equal to NOBATCHACT is the indication of the end of one batch (or event) and the beginning of another.

125 of 136

19. Select the PISubBatches tab, right-click on SubBatch Hierarchy and click Add New SubBatch.

20. Do the following steps: Name the SubBatch OvenSteps. Set the Active Point to use the SimpleMachineStep tag ActivePoint Behavior to use Step and Include zeroth state. Set SubBatch Name Point to Use ActivePoint value

126 of 136

21. Do the following steps: In the Batch Generator MDB View tab, click the Save icon. The PiBaGen interface will not monitor a PIUnit and generate batch data if the PIUnit is not registered. Registering a

PIUnit is like turning the scan option ON for a Historian Tag or Point. Right-click on the Proof_Oven PIUnit and select Register.

22. Do the following steps: Click on Batch Database (see below graphic). Expand the tree until you can see the Proof_Oven unit in the center window. Right-click Proof_Oven and select Search for PIUnitBatch

127 of 136

23. Ensure that the PIUnitBatch search PIUnit field is populated with \\SERVER\BL1\Proof_Oven. If not, enter Proof_Oven.

Tip - If you starting the search from the top of the Batch database tree, then the PIUnit field would contain an *. Need to replace this with Proof_Oven.

24. Click OK.

128 of 136

25. Expand the Batch database search results and verify that Unit Batches are being created by PIBaGen.

26. In the following example, there are 7 Unit Batches. The last unit batch in the list (M1Mix_3246) has PISubBatches 1 finished and 2 still running (you can tell because it is selected and on the right you see End Time is "Still Running"...finished SubBatches would have both Start and End times specified). If you do not see a tree with a plus sign (+) when you searched for PIUnitBatch, you may need to wait a minute or two and search again. Multiple search results will appear in the same window.

Tip - Up to this point you have created a PIUnit and Historian is monitoring and archiving Batch or Event information. The Batch information you have configured is information such as:

* What triggers the start and end of a Batch and Sub Batches their "Active Points"

* Where the value of the Batch ID will come from - the "Unit Batch ID Point"

* A tags value to monitor during the Batch cycles, the "TempZone1 Alias" that you created within the PIUnit

* You have also seen how to monitor basic information of the Batches and Sub Batches, such as Batch IDs and Start and End Times, from within the SMT. In the next section you will see how a BatchView add-on can be used to monitor batch information from within a ProcessBook display.

27. Close the SMT and Administration Console (if still open).

129 of 136

Part D - BatchView

In this exercise, you are going to be looking at a couple of ways to visualize the batch information being generated by the results of the previous parts of this lab. You will 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

1. Go to the CLIENT image.

2. The following steps will build a basic ProcessBook display for our BatchView. Launch ProcessBook.

3. Close the ProcessBook demo file that opens at default.

4. From the File menu select New.

130 of 136

5. Select new ProcessBook Display (.pdi) File, set the Display Name to BatchView, and click OK.

6. Change to build mode by selecting the Build button on the toolbar:

7. Select the Batch Group button on the toolbar:

8. Click and drag a Batch Group into the empty space which covers most of the work area.

131 of 136

9. In the