mi13 factorytalkhistorian se

8/10/2019 MI13 FACTORYTALKHISTORIAN SE

1/140


2/140

Important User Information

This documentation, whether, illustrative, printed, online or electronic (hereinafter Documentation) is intended for use only asa learning aid when using Rockwell Automation approved demonstration hardware, software and firmware. The Documentationshould 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, mandatesthat those responsible for the application and use of those Products must satisfy themselves that all necessary steps have beentaken to ensure that each application and actual use meets all performance and safety requirements, including any applicablelaws, 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) beresponsible or liable for any indirect or consequential damages resulting from the use or application of the Products described inthis Documentation. Rockwell Automation does not assume responsibility or liability for damages of any kind based on thealleged use of, or reliance on, this Documentation.

No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or softwaredescribed 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 isprohibited.

Throughout this manual we use the following notes to make you aware of safety considerations:

Identifies information about practices or circumstancesthat 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, propertydamage, 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/140

3 of 140

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 .................................................................................................... 14

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

Section 1 Performance Equations ............................................................................................................................................... 21

Section 2 - Totalizers ...................................................................................................................................................................... 31

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

Section 1 - Interface Buffering ........................................................................................................................................................ 37

Section 2 - Interface Redundancy ................................................................................................................................................... 44

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

Lab 6 - Backfilling Data into a FactoryTalk Historian SE Server................................................................. 75

Lab 7 Accessing FactoryTalk Historian SE Data via OLEDB .................................................................. 95

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


4/140

4 of 140

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 Start 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 Site Edition 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 powerfulset 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 Excel 2010 32-bit SP1

Microsoft SQL Server 2008 Standard Edition R2

FactoryTalk Historian Site Edition, version 4.0

FactoryTalk VantagePoint, version 5.1

FactoryTalk Historian ProcessBook, version 3.30.02

FactoryTalk Historian BatchView Add-in, version 2012

FactoryTalk Services Platform, version CPR 9 SR 6 SoftLogix, version 20

RSLogix 5000, version 20 (CPR 9 SR 5)

RSLinx Classic, version 2.59 (CPR 9 SR 5)

RSLinx Enterprise, version 5.60 (CPR 9 SR 6)

PI OLEDB, version 2010 R3


5/140

5 of 140

Image configuration/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 alsobeen 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 andFTVantagePoint

Servers, SoftLogixand RSLinx)

CLIENT(FTHistorian and

FTVantagePoint Clients)

Host PC

DATA(FactoryTalk Live Data

Interface)


6/140

6 of 140

Lab 1 - Understanding and Using Exception and Compression

What you will learn:

Edit exception testing to a tag

Edit compression testing to a tag

Trending and displaying the values of tags from the archives to see the differences caused by exception and compression

Part A - Filter Less with Exception/Compression

1. Start on the Clientimage.

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

Histor ian SE > System Management Tools .


7/140

7 of 140

3. Do these steps in this order:

Select Points > Point Builder.

Search for and display the tag ending in *MachineStep .

Click on this tag in the upper pane to make sure it has focus.

Click theArchivetab.

4. Note that this tag currently has default Exception and Compression attributes, unchanged since this tag was

added to Historian from the FactoryTalk Administration Console using Add Individual Historian Points. Verify

these attributes are currently set as follows:

Exception Deviation: 0.25 Eng. Units Compressing: On

Compression Deviation:0.5 Eng. Units

5. Do the following steps in this order:

Select Data > Current Values.

Search for and display the tag ending in *MachineStep .

Click Start Updating.


8/140


9/140

9 of 140

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

12. Wait two minutes to be sure the FTLD Interfacehas enough time to put your changes in effect.

13. Did you wait two minutes?? If not, please wait. If so, go back toData > Archive Editor. Click the Get events

button and scroll to the bottom of your Value - Event Timewindow. 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 (no skipping values):

14. Close the SMT.

Part B - Filter More with Exception/Compression


2. Start System Management Toolsby going to Start > All Programs > Rockwell Software > FactoryTalk



Select Data > Current Values.

Search for and select the tag ending in *SimpleTempZone1.



10/140

10 of 140

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. InSystem Management Tools(SMT), do the following steps in this order:

Go to Data > Archi ve Editor. Search for the tag ending in *SimpleTempZone1.

Change Start time to *-1mto 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 eventsevery minute from the archive for this tag.

6. Minimize the SMTand start VantagePoint Trendby going to Start > All Programs > Rockwell Software >

FactoryTalk VantagePoint > Trend.

7. In the Model, navigate to System > Sources > FactoryTalk > localhos t > Historians > Production Historian

> Tagsand double-click on or drag the tag ending in SimpleTempZone1to the plot surface.


11/140

11 of 140

8. In thisTrend 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. MinimizeTrendand go back to the SMT.


Go to Points > Point Builder.

Search for the tag ending in *SimpleTempZone1.

Click on theArchivetab.

11. When this tag was originally brought into Historian with the FactoryTalk Administration Console, the default

Exception Deviation was 0.25 and Compression Deviation was 0.5. You should still be seeing these default

settings:

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 Savebutton and look for "Successfully edited" message in the Session Record:


12/140

12 of 140

15. Wait for two minutes and then go to Data > Arch ive Editorin the SMTand click the Get eventsbutton. If you

closed the SMTyou 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 Trendthat you had minimized earlier and review how that previous trend appeared.Click the Refreshbutton and you should get an updated trend that looks similar to what you had seen before.

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 their 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:


13/140

13 of 140

20. Turn on Point markersand click OK.

21. See if you can find where the changes you made to your exception/compression took place (you may need tochange 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. In Point Builder, set the attributes on the TempZone1 tag back to the following:

Exception Deviation: 0.25

Compression Deviation: 0.5

23. Be sure to Saveyour changes.

24. Close the SMTand Trendapplications (no need to save the trend).


14/140


15/140

15 of 140

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:

InSystem Management Tools, go to Points > Point Builder. Search for the tag ending in *SimpleTempZone1.

Go to theArch iveTab.

Change CompressingtoOff.

Change ExcMaxto Minutes: 0and Seconds: 10.

5. ClickSaveicon and look for "Successfully edited point" message.

6. Go to the ClassicTab, and change Location3from a 1(Advised Mode) to a0(Polled Mode).


16/140


17/140

17 of 140

Part B - Event Tags


2. Start the System Management Toolsby going to Start > All Programs > Rockwell Software > FactoryTalk


3. Do these steps in this order:

Go to Data > Current Values.

Search for and select the tag ending in *Shift_Timer.ACC.


Notice the value of this tag changing approximately every second.


Select Points > Point Builder.

Search for and display tag ending in *Shift_Timer.ACC. Click on ClassicTab.


18/140


19/140

19 of 140

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 Builderand 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 ClassicTab, change Location3to a 2, in order to make this an OutputTag.

4. Back on the GeneralTab, use the Source tag Searchbutton to select the *Shift_Timer.ACC tag.

5. Saveyour changes.

6. Go back to theData > Current Valuesscreen where you should be still seeing the value of this

Shift_Timer.ACCtag along with the MachineSteptag.

7. To see the actual value of the *StorageDint1output tag in the controller, start FactoryTalk Live Data Test

Clientby going to Start > All Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Live Data

Test Client.

8. Select FactoryTalkand thenNetworkdirectory.

9. Under $Global, select RA Foodsand click OK.

10. Select OKto createGroup1.


20/140

20 of 140

11. Select BL1 > Online, then StorageDint1and finally click OK.

12. Position the Live Data Test Clientover the top of System Management Tools (SMT)such as below. Note that

when the value of the Shift_Timer.ACCchanges (Source Tag), very soon after the StorageDint1tag (OutputTag) is written to with the same value.

13. When done verifying above, close the SMTandFactoryTalk Live Data Test Client.


21/140

21 of 140

Lab 3 - Using Performance Equations and Totalizers


How to use Performance Equations to perform server-side recordable instance and summary calculations.

How to use Totalizers to perform server-side recordable instance and summary calculations.

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).

3. Expand thePointscategory and select the Performance Equationsplug-in. Then, click the Newbutton.


22/140

22 of 140

4. Our first Performance Equation is going to be a Fahrenheit to Celsius conversion. On the Generaltab, 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 Equationtab, set the Equation to the following (Hint: Use the Tag Searchbutton to fill in the tag name. It willautomatically enclose the tag name in single quotes ('), required syntax at the beginning and end of tag names)

('RA Foods:RSLE:BL1.Program:Proof_Oven.SimpleTempZone1' - 32) * 5/9

Click the Evaluatebutton 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:

6. On the Schedulingtab, do the following steps:

Change the radio button to Event-based scheduling.

Use theTag Searchbutton to select the tag SimpleTempZone1.

Change the timestamp assignment option to The timestamp of the triggering event.


23/140

23 of 140

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

7. On theArch ivetab, set the following fields:

Exception Deviation to 0

Compressing toOff

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

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


24/140

24 of 140

9. Do the following steps in the SMT:


Search for and display the two TempZone1 tags (hint: In the Search dialog, do not specify Point Source of FTLD, as

one tag you are looking for is a Performance Equation with Point Source C. You could use Tag Mask of *TempZone1*

for this Search.).

Select Start Updating(if values dont change, please wait 20-30 seconds).

You should see the TempZone 1 Deg CPerformance Equation tag display calculated Celsius values from the source

SimpleTempZone1tags Fahrenheit values.

Part B Using a Performance Equation Functio n

1. Go back to Points > Performance Equationsand click the Newbutton.


25/140

25 of 140

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 Generaltab:

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 Equationtab, do the following steps:

Enter following Equation (Hint: Use Tag Search button to fill in tag name rather than type in!). Note that in the following

equation, the *-1his the Starttime (1 hour ago) and the *is the Endtime (current time)both of these entries need to beenclosed in single quotes ('):

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.

Note: The TimeGT (time greater than) function includes the Tag Name, Starttime, Endtime and Value to begreater than in the parentheses that follow. The result is a value in seconds. In the above, we are dividingby 60 to convert seconds to minutes.


26/140

26 of 140

4. On the Schedulingtab, select Clockschedulingand Scan class of 3which will cause the equation to be

calculated every 30 seconds.

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

5. On theArch ivetab, set the following fields:

Exception Deviation of 0 CompressingOff

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

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

8. Now, we want to open the Performance Equation Schedulingbatch file to see where we could edit, add or

delete scan classes if desired. Go to the SERVERImage.


27/140

27 of 140

9. Start the Interface Configuration Utility(ICU).

10. Click the Create New Interface Instance from .BAT filebutton.

11. Open thepipeschd.batfile located in C:\Program Files\Rockwell Software\FactoryTalkHistorian\Server\bin .


28/140

28 of 140

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 ICUwithout having made any changes.

15. Go back to theCLIENTimage that should still have the SMTopen on the Performance Equations editor.

16. Close the SMT.


29/140

29 of 140

17. Reopen the SMT(have to close and re-open to see this change go into 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 TempZon e1 GT 200 tag.

On the Schedulingtab, 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.

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


30/140

30 of 140



Search for and display tag TempZone1 GT 200.


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.


31/140


32/140

32 of 140

4. We will create a Totalizer to calculate the Moving Time Weighted Average of the Temperature of TempZone1.

Perhaps in the future all of the zone average temperatures could be calculated and compared for determining

maintenance needs, comparing efficiencies, etc.

Start by doing the following steps on the Name & Typetab:

Name of TempZone1 Average Temp

Source tag of SimpleTempZone1(see full tag name below)

Summary calculation of Moving Tim e Weighted Average

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

6. On the Resultstab, do the following:

Select Write final resultsAf ter a time period elapses Results every1 Minute

Write interim resultsAt source t ime (ramp)


33/140

33 of 140

7. On theArch ivetab, do the following:

Exception Deviation of 0

CompressingOff

8. ClickSaveand look for Successfully created totalizer message.



Search for and monitor the tags SimpleTempZone1and TempZone1 Average Temp.


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


34/140

34 of 140

Part B Count Events Totalizer Example

1. In the SMT, go to Points > Totalizersand click the Newbutton.

2. On the Name & Typetab, 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 gonethrough, and we will consider reaching Step 5 a cycle)


35/140

35 of 140

3. On the Resultstab, verify/set the following:

Start schedule at 0 Hour(s)after midnight

Results every1 Hour.

Write interim resultsAt source t ime (ramp).

Note: These settings will cause the Totalizer to accumulate events every hour on the hour, write finalresults 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 endof each hour.

4. OnArch ivetab, set Exception Deviation to 0and Compressing to Off.

5. Savethe Totalizer and look for Successfully created totalizer message.


36/140

36 of 140

6. Add the Machine Cyclesand MachineStep tags to Data > Current Values. Verify Start Updatingis

selected (may have to StopandStart Updatingagain). You should see that every time theMachineStep

reaches5, the Machine Cyclestag increments. If the time on your image is nearing the top of an hour, you

should be able to see the Machine Cyclesreset. If not happening soon, perhaps you can come back later and

watch it occur.

7. When ready to proceed, close the SMT.


37/140

37 of 140

Lab 4 FTLD Interface Buffering and Redundancy


Observe the effect of Interface Buffering in a FactoryTalk Historian system

Understand concepts and advantages of Interface Redundancy

Section 1 - Interface Buffering

1. Select the CLIENTimage.

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

VantagePoint > Trend.


38/140

38 of 140

3. Go to System > Sources > FactoryTalk > localhost > Historians > Production Historian > Tags and click

and drag the SimpleTempZone1tag to the trend surface.

4. Click the Live Modebutton 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 DATAimage.

6. Switch to the DATA image.


39/140

39 of 140

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

FactoryTalk Historian SE > Interface Configuration Utility .

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

9. Once selected, pick Tools > Buffering.

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

11. Select Buffered Serversand notice this interface is configured to buffer data for the historian server we areusing, named SERVER.


40/140

40 of 140

12. ClickOKon the Bufferingdialog and close the ICU.

13. Open aCommand Promptand change to the path of:

C:\Program Files (x86)\Rockwell Software\Factory Talk Histo rian\PIPC\BIN

14. Enter the command: pibufss -qs

Note: pibufss is the buffer service, then there needs to be a space, a - (dash) followed by qs for queuestatistics.

15. The result of this command should be similar to the following. The first column of numbers is the count at thatmoment. The second column is change since last update. Note that you should be accumulatingTotal Event

WritesandTotal Event Reads, but no Current Queue Events at this time.

16. Leave the Command Promptopen and return to the CLIENT image.

17. Verify that your VantagePoint Trendis still displayed and the TempZone1tag is still changing.

18. Go to the SERVERimage.


41/140

41 of 140

19. We will simulate a Historian Server outage by manually stopping Historian.

Stop your Historian Server by selecting Start > All Programs > Rockwell Soft ware > FactoryTalk Histori an SE > Stop

FactoryTalk Historian SE

20. Wait for all of the services to stop and the dialog to close itself before proceeding.

21.After Historian is fully stopped, go back to the CLIENTimage and look at your VantagePoint Trend. When the

Historian Serveris shut down, you will see a break and apparent loss of data".

22. Go back to theDATA image.


42/140

42 of 140

23. Since the Historian Serveris not available, the FTLD Interface is buffering data. You should seeCurrent

Queue Eventsaccumulating (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 His torian SE.

26. While the Serveris 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

Eventsvalue should go to 0 (zero) and the change since last value should be negative. This may take severalminuteseven when the Historian Server is fully running, it may take a couple of minutes for the Interface to

notice and send that buffered data to the server. Please be patient!


43/140

43 of 140

28. Return to the CLIENTimage.

29. Your trend should now be updating with values.

30. If you see a gap, to fully refresh the trend, turn Live Modeoff and back on again. The trend should be

displaying data with no gaps.

31. Leave VantagePoint Trend open andinLive Modefor the next Lab.32. Go to the DATAimage. Make sure the command window has focus and select Ctrl-Cto stop the queue

statistics. Close the command window.


44/140

44 of 140

Section 2 - Interface Redundancy

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

Part A Configu ring Bu ffering and Initi al CLIENT Interface Configuratio n

1. Go to the DATAimage.

2. Open the Interface Configuration Utility (ICU).


45/140

45 of 140

3. Use the ICUon this image to confirm the interface is running (select FTLD1Interface from drop-down list and

look for "Running" at the bottom of the dialog)

4. and configured for Buffering.

5. Close the Bufferingdialog but leave the ICUopen.

6. Go to the CLIENTimage.


46/140

46 of 140

7. On the CLIENT image, we want to verify the connection to the Historian Server named SERVER. Launch the

AboutPI-SDKutility.

8. Click on the Connectionsentry, the SERVERcheckbox and confirm SERVER connecteddialog appears at

bottom.


47/140

47 of 140

9. Select File > Exit PISDKUtilit yto close theAboutPI-SDK.

10. Launch the Interface Configuration Utility (ICU).

11. Click the Create new Interface Instance from .BAT filetoolbar button.


48/140

48 of 140

12. Navigate to the LDInterfacedirectory and select the FTLDInt_FTLD.bat.bakfile. Click theOpenbutton.

13. You will be prompted to select the Host PI Server. Select SERVERfrom the drop-down box and click the OK

button.

14. Note that the Interface IDis set to the default value of 1and will be the same ID as that of our primary interface

onDATA, Interface ID of 1.


49/140

49 of 140


Select the Servicecategory.

Change the Display name to FTLD1.

Click the service Createbutton.

16. Select Tools > Buffering.

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

18. Read the messages and clickOK (you will not start the service YET!).


50/140

50 of 140

19. You should be taken to the Buffered Serversdialog. Select SERVERfrom the drop-down box. Click the OK

button.

20. Read the following and click Yes.


51/140

51 of 140

21. First, click Generaland then click Serviceon the left. ClickYesmake 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 prompted it to appear now to get out of the way.

22. Some of the settings made when configuring the FTLD Interface on the DATAimage (prior to this lab) was to

delete some unneeded Scan Classesand enable Disconnected Startup. Disconnected Startupis a

recommended feature to allow an Interface to start collecting data when it starts, even if it doesnt have a

connection to a Historian Server (it will collect and buffer). To make this interface match, first go to the

Generaltab, click on them one at a time and use the Remove selected scan classbutton to delete scan

classes0.05, 0.1and0.25.

23. You scan classes should now appear as follows.


52/140

52 of 140

24. Click on Disconnected Startupcategory and select Enable disconnected startup (with point caching).

25. Leave the ICUopen.

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 theSERVERimage.

Note: 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 trainingpurposes in this lab.

2. Go to Start > Adminis trative Tools > Share and Storage Management.

3. Click on Provision Shareon right side of dialog.


53/140

53 of 140

4. Click the Browsebutton.

5. Click the c$drive and thenMake New Folderbutton.

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


54/140

54 of 140

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

Note: In a real application, you may wish to adjust these permissions for a different user name or group ofusers.

8. ClickNext >on dialog that follows and then Createon this dialog.

9. ClickCloseand then close the Share and Storage Managementdialog.


55/140

55 of 140

Part C Configuring Interfaces for Failover

1. Change to the DATAimage which should still have its ICUopen.


Select the Failoversub-category under UniIntin the left pane.

Check the box to Enable UniInt Failover.

Select Phase 2.

For Synchronization File Path, browse to the FTH_Sharedfolder on Server (Network > SERVER > FTH_Shared)

and click Open. The fileFTLDInt_FTLD_1.datwill be created in this folder. If for some reason you cannot Browse,

type \\SERVER\FTH_Shared\FTLDInt_FTLD_1.datinto this field.

Select UFO (UniversalFailOver) Typeof HOT.

Carefully confirm all following selections. When confirmed (are you sure?), selectApply.

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


56/140

56 of 140

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

5. Go to the CLIENTimage.

6. Make the same Failoverselections on this interface as you did on the other.

7. HOWEVER - Select Failover ID # 2for this instance and Failover ID # 1for the other instance - IMPORTANT!

Verify all below selections CAREFULLY!

8. Are you sure the settings match especiallyFailover ID# for this inst ance of 2 and other instance of 1?

If so, clickApplyon above dialog

9. Read and click OK.


57/140

57 of 140

Part D Modify ing FTLD Servic e Properties

1. Still on the CLIENTimage, go to Servicesby selecting Start > Control Panel > System and Securi ty >

Administ rat ive Tools > Services.

2. Double-click the FTLD1Service.

3. Select the Log Ontab, and specify to useAdminist ratoraccount with password of rockwell. Click OK.



58/140

58 of 140

5. Close Services,Administ rat ive Tools and Systemand Securitydialogs.


7. Go to Services(Start > Administrative Tools > Services) and make the same changes to the FTLD1serviceon this image. UseAdminist ratorwith password of rockwell. Click OK.



59/140

59 of 140

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

10. Close the Servicesdialog.

Part E Finishi ng up and Testing the Interface Redundancy


2. In the ICU, click the Browsebutton to select the other instance.

3. Click the FTLDInt1interface on the CLIENTimage and click OK.


60/140

60 of 140

4. In the tag area, below where you identified the UFO TypeandSynchronization File Path, right-click on the

tags and select Create UFO_State Digital Set on Server SERVER:

5. Read and click OKon this dialog.

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

7. Click theApplybutton at the bottom-right of the dialog box and click OKon the Interface Changes Require

Restartdialog box that will appear.

8. Restart the interface. Look for Stopping Service, then Starting Serviceand then Readyand Runningat the

bottom-left of the dialog box. Leave the ICUopen.

9. Return to the CLIENTimage.

10. Select the below Browsebutton.


61/140

61 of 140

11. Click the interface on DATAimage and click OK

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

service.

13. Switch over to the SERVERimage.


62/140

62 of 140

14. Launch System Management Tools(SMT).

15. Expand the Datacategory and select the Current Values plug-in.

16. 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 Interface Node with Failover ID#1 is currently "Primary" and sending data to Historian Server

DeviceStatus = 0 Zero is good status

Heartbeats = Incrementing numbers indicate Interface Nodes #1 and #2 are responsive

States = Current Primary or Backup state of Interface Nodes #1 and #2. Under certain conditions couldalso indicate Off or Transition


63/140

63 of 140

17. Leaving the SMTopen, go to the CLIENTimage and the VantagePoint Trendapplication, which should still be

running from the previous lab. You may see a gap or loss of data from interface configuration changes and

restarts. If not running, start VantagePoint Trendand create a display with a trend of the tag ending in

SimpleTempZone1.

Note: Since the Interface on the DATA image is currently Primary (you should have seen that with the SMTon the SERVER image), this tag being trended is coming from the Interface on the DATA image to theHistorian Server.

18. On the DATAimage, use the ICUto stop the Interface by clicking Stop interface service.


64/140

64 of 140

19. Back on the CLIENTimage, 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.

20. Start the Interface again on the DATAimage.

21. Switch back to the SERVERimage.

22. Did the Interfaces switch roles? The Interface onCLIENT(Failover ID #2) is now Primary and the Interface

onDATA(Failover ID #1) is Backup?

23. 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. YouWILL FOR SURElose data then!


65/140

65 of 140

24. 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 CLIENTimage, stop the Interface with the ICU, then close the ICU.

Use the ICU on DATAimage to de-select Enable UniInt Failover, clickApplyand Restart the Interface Node.

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


66/140

66 of 140

Lab 5 - Using and Displaying Audi t Information


UseSMTto enable auditing of your FactoryTalk Historian SE Server

UseAudi tViewerto examine activity

Note: This lab uses AuditViewer to display audit information. This tool is not installed automatically, butincluded in Redist/AuditViewer folder in Historian 3.0 and newer install media and/or downloaded fromKnowledgebase article 64384 - FactoryTalk Historian Site Edition AuditViewer.

Also note that AuditViewer has already been installed on the SERVER image.

Part A - Enable Audi ting o f your PI Server

1. Go to the SERVER image:

2. Launch the System Management Tools(SMT).


67/140

67 of 140


Expand the Operations category and select Tuning Parameters.

Click the EnableAudit Tuning Parameter.

Note:The Auditing Mask entered value is a bit mask where each bit refers to a specific database. -1enables the audit of all databases. Masked parameter (Point:1, Digital Sets:2, Attribute Sets:4, PointClass: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.


68/140

68 of 140

4. Double-click on EnableAuditto display the dialog window. Change the auditingValueto -1and 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.


69/140

69 of 140

7. Once all of the services have stopped and window has closed, select Start > All Programs > Rockwell

Software > FactoryTalk Histori an SE > Start Factory Talk Historian SE. Wait for all services to start and

window to close.

Part B - Make Changes and Use Audi t Viewer to Examine the Acti vity

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 theSMT, expand the Datacategory and selectArch ive 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 *).


70/140

70 of 140

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 Saveicon . The modified value will be displayed

and marked as substituted (scroll to your date/timestamp and look for checkmark in Substitutedcolumn after these steps).


71/140

71 of 140


Go to Points > Point Builder.

Search for tag BA:LEVEL.1.

Go toArch iveTab.

Change Spanto 101.

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

6. From theSMT Tools menu selectAudi t Viewerto launch the application.


72/140

72 of 140


From theAudi tViewer, expand the Managesection. Verify theArch ive 0checkbox is checked (if not, check it) and

then click the Managelink

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

8. From the subsystem details page scan each of the files in turn by selecting the Scan Filebutton from each ofthe three subsystem views. Do all three (only two shown below).


73/140

73 of 140

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

10. You can also view this in table form. Above the three Subsystems listed select the Tabletab.


74/140

74 of 140

11. Do these steps:

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

Select Searchto display and audit records for the time period specified.

Note: 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.

12. 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. You should see entries such as:

Configuration (Base) tab:

Timeseries (Snapshot/Archive) tab:

13.As time allows, make other FactoryTalk Historianedits/changes and detect them withAudi tViewer.

14. CloseAudi tViewerand the SMT.


75/140

75 of 140

Lab 6 - Backfilli ng Data into a FactoryTalk Historian SE Server


Understand configurations necessary before backfilling data

Use example of UFL Interface to backfill data from a CSV file

Part A - Overview of Data to Backfill and Historian SE Configuration

In this lab you will create a new tag in FactoryTalk Historian, and FactoryTalk Historian will start collecting values and

timestamps for that tag from that time forward. However, we will assume you previously had collected values and timestamps

from that very same tag from another method, and have a CSV file of this previously collected data to backfill into the

FactoryTalk Historian archives.

1. Go to the SERVERimage.

2. Go the Start > All Programs > Rockwell Softwareand openFactoryTalk Administration Console.

3. After selecting Networkdirectory, right-click on RA Foodsand selectAdd Individual Histor ian Points.


76/140

76 of 140

4. ClickBrowse Tags.


In the left pane, navigate to RA Foods > BL1 > Online > Program:Proof_Ovenand click on OvenUDT.

Click on TempZone1in the right pane.

ClickAdd Tag(s) to L is t.

6. After confirming this tag is in the lower pane, click OK.

7. ClickOKagain onAdd Historian Pointsdialog and close FactoryTalk Administ ration Console.


77/140

77 of 140

8. Now we will take a look at a couple of CSV files that will be used to backfill data for this new tag. Do the

following steps:

Use Windows Explorer and go to C:\Class Files\Backfill Lab.

Right-click on Data to Backfill.csv.

Select Open with > Notepad.

9. Scroll through this CSV file and note that it contains over 4000 entries (dont bother counting!) of timestamps(date followed by time) and values between May 1 and May 31, 2012, for a tag by the name of:

RA Foods:RSLE:BL1.Program:Proof_Oven.OvenUDT.TempZone1

This is a CSV (comma delimited) file, with each line formatted as:

Tagname,Timestamp,Value

10. We will use the data in the Data to Backfill.csvfile to backfill data in a FactoryTalk Historian archive. Later in

this lab, when you configure a Universal File and Stream Loading (UFL) interface, you will specify this file as the

source of the data. However, we will also need a reference file to show how the data to be backfilled is

formatted. We could use the same file, but a reference file is limited to 50KB in size, so we will use a different

file instead.

Back in Windows Explorer, right click on the Backfill File Reference.csv.

Select Open with > Notepad.


78/140

78 of 140

11. Note that this file has only one line in it, and the formatting of the line matches the lines in the Data to

Backfill.csvfile. ThisBackfill File Reference.csvfile will be used when configuring an INI file needed for the

UFL interface (you will see all of this as you continue with the lab).


Close both csv files and DO NOTsave any changes if asked.

Minimize Windows Explorer.

13. Open System Management Tools(SMT) by going to Start > All Programs > Rockwell Software >

FactoryTalk Historian SE > System Management Tools.

14. The first thing we will do is look to see if there is already data in the Historian archives for this tag within the

timeframe of the data in the CSV file (May 1 31, 2012). There shouldnt be, because you just created that tag!

Go to Data > Archi ve Editor.

Click the Tag searchbutton.


79/140


80/140

80 of 140

18. If we are going to backfill data from the CSV file, which contains values and timestamps from May 1 31, 2012,

we need to make sure one or more archives exist that will be able to hold such data. Go toOperation >

Arch ives(under System Management). The list of your archive(s) should be similar to the below. If you look

at the Start Time and End Times, you currently do not have an archive able to contain data from May of 2012.

19. Since the required archive does not exist, lets create it. Do these steps in this order:

Click the Create a new archivebutton (dialog shown below will then appear).

Give it a name of BackfilledArchive(nothing special about this name, could be any name you like).

Select Create archive with fixed start and end time.

Enter Start time of 5/1/2012 12:00:00 AM (we could pick a date further in the past, like 1/1/2012 if we want to use this

archive for even older data, but for the purpose of this lab we will make it start at 5/1/2012).

Enter End time of 12/31/2012 11:59:59 PM(this archive can now contain data up to the end of 2012 in case we want

to backfill additional data later).

Select archive Type of Dynamic.

After confirming below settings, click OK.


81/140

81 of 140

20. You should see your archive was created to contain data within the timeframe specified. Also, note the

successfully created message.

21. Now we will create two Trustsfor the FactoryTalk Historian Server to allow the UFL interface to interact with the

Server/Archives.

Go to Security > Mappings & Trusts.

Click the Truststab.


Click the down-arrow next to the Newbutton.

ClickAdvanced .


82/140

82 of 140


Enter Trust Name ofPI_UFL(could actually name whatever you want).

Enter Application Name of PI_UFL.exe (this is the PI-SDK Application for this interface).

Click PI Identity browsebutton.

24. You would normally use a different existing Identity, Group or PI User with more restrictive privileges, or even

create a special one for this interface to use (see documentation), but for the purpose of this lab, do thefollowing:

Select Type of PI Users.

Select piadmin.

Click OK.


83/140

83 of 140

25. Your dialog should now look like this. Click OK.

26. You should see your trust added as follows:

27. Repeat previous steps to create another trust named PI_UE(could be whatever you want), trusting application

PI_UE(this is the PI-API Application for this interface does not have .exe extension) and PI Identity of piadmin.

Enter Trust Name ofPI_UE.

Application Name of PI_UE.

PI Identity of piadmin.

Click OK.


84/140

84 of 140

28. You should now have these two Trusts in your Historian Server.

29. Minimize the SMTfor later use.

Part B - Configu re, Run and See Results of UFL Interface

1. Open Interface Configuration Utility(ICU) by going to Start > All Programs > Rockwell Software >

FactoryTalk Historian SE > Interface Configuration Utility .

2. Select Interface > New Windows Interface Instance from EXE

3. ClickBrowse


85/140

85 of 140

4. Go to C:\Program Files (x86) > Rockwell Software > FactoryTalk His torian > PIPC > Interfaces > PI_UFL.

Select PI_UFL.exe.

Click Open(not shown below).


Select SERVERfrom the drop-down list.

Specify Point Source of FTLD.

ClickAdd. You will see a message that the interface is ready to be configured (not shown below) click OK on that message).

6. ClickUFLtab and browsebutton for the Configuration File.


86/140

86 of 140

7. You are identifying an INI file that the UFL interface will use to store its configuration. If you had an existing one

you wanted to use, you could select it. We do not, so are going to create a new file and configure it in the next

several steps.

Go to the INIfolder in the PI_UFLdirectory.

Enter name of MyBackfill.

Click Open.

8. Click the Launch UFLDesigner.exebutton to step through configuration of our INI file.

9. Read message and click Yes.


87/140

87 of 140


Leave default Plug-in ofAsci iFi les .dl lselected. This is because we are going to backfill from an ASCII (CSV) text file.

Usebrowsebutton and select the reference file of C:\Class Files\Backfill Lab\Backfill File Reference.csv.

Remember from earlier in this lab, this file contains one line of text that matches the formatting in the data file we will

use to backfill from and will be used as a reference as we continue with this configuration.

Click OK.

11. You will see three panes in this editor. Configurations are done in the left-pane, the center-pane displays our

reference file contents, and the right-pane shows the actual INI file contents as it is being created.

12. In the configuration pane, notice we are on tab 1 Generaland the Input File Mask is defaulting to the same

Backfill File Reference.csvfile that we picked in a previous step. This would be OK if our actual data to import

is the same file we used for a reference. However, reference files have a 50KB maximum size and our file of

data for backfilling is much larger than that, so in the next step we will have to pick the actual data file.

13. Click in the Input File Maskfield so that the browse button will appear. Click the browsebutton.


88/140

88 of 140

14. Go to C:\Class Files\Backfill Lab\

Select Data to Backfill.csv.

Click Save.

15. ClickYes.

16. The top of your configuration pane should now have the Data to Backfill.csvfile specified for Input File Mask. Click the blue right-arrow to go to tab 2 Variables.

17. This tab is used to define the variables or parts to be extracted from the csv file. Click the green+button to

add the first variable.


89/140


90/140

90 of 140


Enter Name of Value.

Select Data Type (using drop-down arrow) of Number.

When done with above, click blue right-arrow to go to tab 3 Message Types.

21. Click the green +sign to add a Message Type. Leave this configuration as it is. It basically is indicating that

any first character in a line is the beginning of the data for that row. C1==* is interpreted as the first

character in a row (Character 1 or C1) can be anything (wildcard of *) to indicate the start of data for that row.

22. Go to tab 4 Data Extract ionby clicking blue right-arrow.

23. This tab is used to assign data extraction to specific variables. Click the green+button.


91/140

91 of 140

24. The data in our CSV file is delimited, so select DelimitedandNext.

25. The data in our CSV file is delimited with commas, so check Comma. Notice in the Data preview window you

can see the data is properly delimited (you can tell by the black vertical lines), separated by the commas

between Tagname, Timestampand Value.

Click Next.

26. Read the blue text in this dialog carefully.

One at a time, drag the Tagname, Timestampand Valuevariables to the appropriate columns in the Data preview.

When the three variables are in the proper columns as shown below (review carefully!), click Finish.

27. Click blue right-arrow to go to tab 5 Actions.


92/140

92 of 140

28. On the5 Actionstab, click the green + sign.

29. Read the blue text. Leave the StoreInPIoption selected. Similar to the previous steps, drag the three variables

to the appropriate place in the Resultfield (you will be dragging and dropping on top of).

Tagname to

Timestamp to

Value to

30.After above step, theResultfield should appear as follows:

31. ClickValidateand you should get a green shield.


First, clickAdd.

Second, click Close.


93/140

93 of 140

33. Click the Saveicon and then select File > Exitto close the UFLDesigner.

34. Back on the ICU, go to the Generaltab

Click theAdd a scan class button.

Specify a 30 second scan class by entering 00:00:30 (in a real application this may differ).


Go to Servicetab.

ClickApply.

Click Create(will take a few seconds).

Click Start interface service.

36. In a few seconds you should see ReadyandRunningin the lower left-hand corner.


94/140

94 of 140

37. Restore the Windows Explorer you minimized earlier. When all 4000+ values and timestamps are finished being

transferred to the FactoryTalk Historian Server, the current date, time and a ._OKextension will be appended to

the name of the source data file.

38. Restore the SMTthat you minimized earlier.

Go to Data > Archi ve Editor.

Click Get Events(green arrow).

With5/1/2012and *as Start and End times, you should now be able to see all of the data youve backfilled into theHistorian archives. We originally had 20-200 or so events for this tag within this time frame. Now, you should be seeing

4000-5000eventsthe 4000+ you backfilled, plus the more current values that Historian has been collecting.

Congratulations!!

39. Scroll through and briefly review the data collected from May 1, 2012 to May 31, 2012, now in the Historian

archive. You will have a large gap from May 31, 2012 to whatever the current date is (the date you are doing

this lab), but youve successfully backfilled data into a Historian archive.

40. On the ICU, stop the UFLinterface.

41. Close ICU, SMTand any open dialogs/windows.


95/140

95 of 140

Lab 7 Accessing FactoryTalk Historian SE Data via OLEDB


Understand capabilities of using PIOLEDB Provider

Configure Reporting Services to display a report based on FactoryTalk Historian data

Part A - Using PIOLEDB.msc

1. Go to the SERVERimage (this is where PIOLEDB Provider is installed).

2. Use Windows Explorer, go to the following path and double-click on the PIOLEDB.mscapplication :

C:\Program Files (x86)\Rockwell Software\Factory Talk His torian\PIPC\OLEDB\Tools\MMC.

3. Under PI Servers, right-click on SERVERand select Connect.

4. Select the Use Windows NT Integrated securitycheckbox and then clickOK.


96/140

96 of 140

5. If you get an error of some kind, repeat last two steps. Expand thepiarchivecatalog and click on the picomp

table. Observe the sample query that appears and the resulting tag, timestamps and values (you will have

different timestamps, values, and may have more or less resulting records listed).

6. Right-click on picompand select Query.

7. Verify the default columns that are configured to be displayed and the default query that is configured to display

information from the sinusoidtag from the last hour (*-1h represents one hour ago and *represents now).


97/140

97 of 140

8. Select svalue, statusand flags, one at a time, and move them to the left by clicking


98/140

98 of 140

11. You should see final query and results displayed. Only tag , timeandvaluecolumns are shown and values for

last 20 minutes of BA:TEMP.1tag. You may have more or less records listed, maybe only 2-3.

12. Take a few minutes to experiment with other catalogs, tables, edited queries, etc.

13. Close PIOLEDB.mscand dont save settings when ready to proceed.

Part B - Using PIOLEDBTester.exe

1. Stay on the SERVERimage.

2. Use Windows Explorer to launch the PIOLEDBTester.exeapplication by double-clicking on it from the following:

C:\Program Files (x86)\Rockwell Software\FactoryTalk His torian\PIPC\OLEDB\Tools\PI OLEDB Tester.

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


99/140

99 of 140

4. Select Sample Statements >>.

5. In theArch ive Statementscategory, 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 types

of situations such as the following:

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 Statementsand click Execute. Review results displayed at the bottom of the

dialog.

7. Try editing one of the SQL Statementsor entering one of your own, executing and reviewing results.

8. Close PI OLEDB Testerand any open dialogs or windows.


100/140

100 of 140

Part C - Using Microsoft Reporting Services

1. Verify that you are on the SERVER image.

2. From theStart Menu, launch SQL Server Business Intelligence Development Studioby selecting Start > All

Programs > Microsoft SQL Server 2008 R2 > SQL Server Bus iness Intell igence Development Studio.

3. On the Filemenu, point to New, and then click Project


101/140

101 of 140

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

5. In the Templates list, clickReport Server Project.

6. In the Name field, enter FTH MSRepor t.

7. ClickOKto create the project.

8. TheFTH MSReportsolution 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. Right-click FTH MSReport and click Properties.


102/140

102 of 140

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

11. ClickOK.

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

12. Right-click the Shared Data Sourc esfolder and selectAdd New Data Source.


103/140

103 of 140

13. TheShared Data Sourcedialog box appears.

14. Enter PIOLEDB in the Name field.

15. Select OLE DBfrom the Typedrop-down list.

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

17. Select OLE Providerof PI OLE DB Prov iderfrom the drop-down list.

18. Enter SERVERinto Server or file name field.

19. Specify Use Windows NT Integrated Security .

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


104/140

104 of 140

21. ClickTest Connection.

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

23.Add the following to theConnection string:

;Integrated Security = SSPI

24. Verify the above configuration options and click OK.

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

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

Item...


105/140

105 of 140

27. Select Report Wizard.

28. InNamefield, leave the default name Report1.rdl.

29. ClickAdd.

30. TheReport Wizardwelcome page will be displayed. Click Next.


106/140

106 of 140

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

32. ClickNext.

33. In the design query type the following:

SELECT tag, time, value

FROM piarchive..picomp

WHERE tag LIKE ? A ND time >= ? AND time


107/140

107 of 140

36. ClickNext.

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

38. Select timeand clickGroup>to move time into the Group display field.

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

40. Verify that the following groups have been configured.

41. ClickNext.

42. Select the default Stepped.

43. ClickNext.

44. Select the default Slate.

45. ClickNext.


108/140

108 of 140

46. InReport Namefield, leave the default report name Report1.

47. ClickFinish.

48.A view opens that contains DesignandPreviewtabs; the report opens in Design view (may need to click on

Designto give it focus).

49. From theReport Datawindow on the left, under Parameters, double-click onParameter1.


109/140

109 of 140

50. Configure the Parameter1properties with the following settings:

Prompt: Tag Mask

Data type: Text

Click OK.

51. Repeat the parameter configuration steps for Parameter2with the following settings:

Prompt: Start Time

Data type: Date/Time

52. Repeat the parameter configuration steps for Parameter3with the following settings:

Prompt: End Time

Data type: Date/Time

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


110/140

110 of 140

54. Set the parameters to the following (see below graphic). Note that CDT158is an internal test tag that exists by

default in FactoryTalk Historian SE:

Tag Mask: CDT158

Start Time: Date and Time of 20 minutes ago(for example, 4/16/2014 9:33:00 AM)

End Time: Date of tomorrow

55. ClickView Reportand observe the results.

56. Within the above window, if you cursor down you should be able to see several timestamps and values that were

archived over the last 20 minutes. If youd like to see more data, and your images have been running for morethan 20 minutes, you could try changing your Start Timeto 30 minutes ago, 1 hour ago or some other time in

the past and click View Reportagain.

57. In the Solution Explorer on the right side of Visual Studio, right-click on FTH MSReportand select Deploy.

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


111/140

111 of 140

59. Right-click on the Report1.rdlreport and select Deploy.

60. Watch for succeeded messages.

61. Close Visual Studio.

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


112/140

112 of 140

63. Type in address of http://SERVER/Reports .

64. ClickFTH MSReport.

65. ClickReport1.

66. Set the parameters to the following, then click View Report:

Tag Mask: CDT158

Start Time: Date and Time of 20 minutes ago(for example, 4/16/2014 9:40:00 AM)

End Time: Date of t omorrow

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

68. Close Internet Explorer.


113/140

113 of 140

Lab 8 - Configuring Event Framing and Using BatchView


Configure PIBaGen to populate batches

Configure a BatchView Group in ProcessBook

Compare a sub-batch phase against a golden batch

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 VantagePointfor this type of modeling and asset organization.

1. Verify that you are on the SERVERimage:

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

Wizard.


114/140

114 of 140

3. Read the Welcomedialog and click Next.


ClickAnalyze.

Verifyno issues found message appears.

Click Next(Next button not shown below).

5. Click the AF Server Connectbutton.

6. Click the AF Database Browsebutton.


115/140

115 of 140

7. ClickNew Database.

8. Accept default name of Database1and click OK.

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

10. ClickNext.


116/140

116 of 140

11. Read this message and click Yes.

12. ClickFinishon below dialog and Congratulations!

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

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


117/140

117 of 140

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

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


118/140

118 of 140

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

InSync.

18. Close the SMT.

Part B - Configuring PIBaGen

1. Verify that you are on the SERVERimage.


119/140

119 of 140

2. Launch the Interface Configuration Utility(ICU).

3. Click the Import Existing Interface from .BAT filetoolbar 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.

6. The Interface will be named: PIBaGen.

7. Change the type from nonetoother_non_uniint.


120/140

120 of 140

8. From the ICUtoolbar click Save.

9. ClickYesto continue when warned that no point source has been specified.

10. In the Servicearea, setStartup Type toAuto and click theApply button. Click Yesif you get the message Do

you wish to proceed without specifying a Point Source?

11. Click the Startbutton on the toolbar. Click Yesif asked Do you wish to proceed with interface startup without

defining scan classes?


121/140

121 of 140

12. Go to Start > All Programs > Administrative Tools > Services and check that the newly created PIBaGen

service is Started (look for PI Batch Generator Interface).

13. Close the Servicesdialog and close the ICU.

14. Use Windows Explorer to navigate to the directory C:\Program Files\Rockwell Software\FactoryTalk

Historian\Server\adm. Look closely for these two files which you will edit in the following steps.

pisrvsitestart.bat

pisrvsitestop.bat

15. Right-click on pisrvsitestart.bat and select Editfrom the context menu.

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


122/140

122 of 140

17. Savethe file and CloseNotepad.

18. Right-click on pisrvsitestop.batand select Editfrom the context menu.

19. Remove theREMstatement from in front of net stop pi bagen.

20. Saveand CloseNotepad.

21. Close Windows Explorer.

Part C - Create a new PIUnit

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


123/140

123 of 140


Expand the Operationcategory and select Module Database.

UnderSERVER, right-click on Modulesand select New.

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

4. Right-click on BL1module and select New > PIUnit.

Ste

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


124/140

124 of 140

6. Assign an aliasto the Proof_OvenPIUnitright-click on Proof_Ovenand create a newAlias.

7. Enter TempZone1 into theAlias Namefield and map it to the PI Server named SERVERand tag ending in

SimpleTempZone1(use the Searchbutton), and click OK.

8. Your Module Database should appear as follows:

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

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

Administ rat ion Console).

10. ClickNetworkdirectory and OK.


125/140

125 of 140

11. In the FactoryTalk Administration Console, right-click RA Foodsand clickAdd Individual Histor ian

Points

12. Select Browse Tags


126/140

126 of 140


BrowseRA Foods > BL1 > Online > Program:Proof_Oven > SimpleBatchID(full path or tree not able to be shown

below).

Select the tag SimpleBatchIDon the right.

ClickAdd 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. ClickOK on

this dialog (OKbutton not shown).

15. CloseAdminist rat ion Consoleand switch back to System Management Tools(SMT).


127/140

127 of 140


Expand the Batchcategory and select Batch Generator.

Select SERVERin the middle pane under Registered Units Only tab (see below graphic).

Select the Interfacetab in the right pane.

Set the Configuration Module Name to PIBaGen.

In the middle pane, click the Savetoolbar button.

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


128/140

128 of 140

18. Using Ba

mi13 factorytalkhistorian se

Documents