RSTechED 2011
MI07 FactoryTalk Transaction Manager
Publication Number -- Date Copyright 2011 Rockwell Automation, Inc.
MI07 FactoryTalk Transaction Manager
Contents
Before you begin ......................................................................................................................................... 4
About this lab ................................................................................................................................................ 4
Tools & prerequisites .................................................................................................................................... 4
Exercise 1: Work order tracking ................................................................................................................ 5
Create a new configuration ........................................................................................................................... 5
Defining the connection to the control system .............................................................................................. 7
Defining the connection to the database ....................................................................................................... 9
Connecting control system to database ...................................................................................................... 16
Testing the configuration ............................................................................................................................. 21
Exercise 2: Parameter Download / Recipe Management ...................................................................... 27
Adding points to an existing configuration .................................................................................................. 27
Adding data objects to an existing configuration ........................................................................................ 30
Adding a transaction to an existing configuration ....................................................................................... 31
Testing the modified configuration .............................................................................................................. 35
Exercise 3: Duplicating transactions ...................................................................................................... 37
Exporting existing configuration data .......................................................................................................... 37
Editing the exported file............................................................................................................................... 39
Importing new configuration data ................................................................................................................ 42
Exercise 4: Buffered data collection ....................................................................................................... 45
Duplicating points with Excel....................................................................................................................... 45
Adding a new data object ............................................................................................................................ 49
2 of 62
Exporting a transaction template ................................................................................................................ 50
Building a transaction in Excel .................................................................................................................... 53
Importing a nearly complete transaction ..................................................................................................... 57
Completing the imported transaction .......................................................................................................... 58
Conclusion ................................................................................................................................................. 62
3 of 62
Before you begin
Launch the FactoryTalk Transaction Manager. A shortcut to it can be found on your desktop or it can be
run from the Start -> All Programs -> Rockwell Software -> FactoryTalk Transaction Manager ->
FactoryTalk Transaction Manager menu item.
About this lab
FactoryTalk Transaction Manager is a server based tool for managing the flow of data from the control
system to a database and back again. Applications where Transaction Manager can be deployed range
far beyond the simple data collection scenario.
The goal of this lab is to demonstrate some of the types of advanced tasks that can be accomplished with
the product and to explore the tools available to help create and manage larger configurations quickly and
easily.
This lab is intended to be done in sequence; however provisions have been made to allow individual
exercises to be skipped if necessary.
Tools & prerequisites
Software programs required
FactoryTalk Transaction Manager 10.00
FactoryTalk View SE 5.10
RSLogix 5000 v17
SoftLogix 5800 v17
Microsoft Office Excel 2008
Microsoft SQL Server Standard 2008
VMware Workstation 7.1.4, VMware Player 3.0.1 or VMware Fusion 3.1.0
4 of 62
Exercise 1: Work order tracking
In many manufacturing systems, it is desirable to know where partially built products are at various times.
Tracking work in progress can help reduce inventory, identify bottlenecks in the process and highlight
areas where efficiency can be improved. Tracking WIP is often an important piece of migrating from a
build to inventory to a build to order model and can help reduce the amount of wasted raw materials.
To this end, exercise 1 will pair FactoryTalk Transaction Manager with a stored procedure to retrieve a
manufacturing order for a work station and record the time that the order was received by the first station
and the time that the order was completed by that station. When completed, an operator will be able to
pull the next work order from the database from the HMI terminal and allow the control system to
automatically update the work order status when complete.
Create a new configuration
The first step in a Transaction Manager deployment is creating a configuration and setting the interface to
the control system and database. Typical applications will leverage FactoryTalk LiveData to interface with
rd
any number of Rockwell and 3 party OPC servers and either ODBC or OLE-DB to interface to a SQL
Server database.
In the FactoryTalk Transaction Manager user interface, select New from the Configuration
menu
In the Configuration Name field enter MI10_Config and click Step 1
In the Path field enter C:\Lab Files\MI10_Config.
Check Enable Online Edits
Check Microsoft OLE-DB
5 of 62
Click Apply
Click OK on the Insert Success dialog then Close to return to the configuration checklist
Click Step 2
In the Password field enter rockwell and click Apply
Click Yes on Update Warning dialog. Then click OK on the Update Success dialog.
6 of 62
From the Connector Service drop down box, select OLEDB Connectors
In the Connector Name field enter OLEDB
Note that the password field has already been populated and click Apply (note: if the password
field is blank, enter rockwell)
Click OK on the Insert Success dialog then Close to return to the configuration checklist
Defining the connection to the control system
Once the framework of the configuration has been defined, the connections to the control system can be
created. The controller and HMI project for this lab contains 3 work stations in a fictional manufacturing
plant. Below is a list of controller tags and their uses in this exercise:
Trigger Transaction Manager to send
/Devices::[MI10_Control]Station1.NextGet
the next manufacturing order
Acknowledge that the next
/Devices::[MI10_Control]Station1.ReturnGetNext
manufacturing order has been sent
Acknowledge that the build complete
/Devices::[MI10_Control]Station1.ReturnStationOut
time has been logged
Trigger Transaction Manager to log
/Devices::[MI10_Control]Station1.BuildTimer.DN
that work in this station is complete
String to hold the manufacturing order
/Devices::[MI10_Control]Station1.MfgOrder
number
String to hold the part number for the
/Devices::[MI10_Control]Station1.PartID
current manufacturing order.
With these controller tags identified, the next step in configuring Transaction Manager is to define the
data points, and their collection parameters.
7 of 62
Click Step 3
In the Select An Application window, select RSTechED2010 and click OK
In the tag browser find and add the following tags:
/Devices::[MI10_Control]Station1.NextGet
/Devices::[MI10_Control]Station1.ReturnGetNext
/Devices::[MI10_Control]Station1.ReturnStationOut
/Devices::[MI10_Control]Station1.BuildTimer.DN
/Devices::[MI10_Control]Station1.MfgOrder
/Devices::[MI10_Control]Station1.PartID
(Note: The BuildTimer.DN, MfgOrder, and PartID tags can be found in their own sub-
folders.)
8 of 62
Change the mode of /Devices::[MI10_Control]Station1.NextGet and
/Devices::[MI10_Control]Station1.BuildTimer.DN to Unscheduled
Change the mode of the other tags to Device-Sched
Click Apply to save changes and then Close to return to the configuration checklist
Defining the connection to the database
The production management database for this lab is a very simple model. This exercise makes use of a
9 of 62
table containing manufacturing orders and a stored procedure to pull the next available order for the first
station. Transaction Manager can interface directly with a variety of database table designs and perform
single row inserts or updates. More complicated operations and integrations can be wrapped in a stored
procedure and exposed to Transaction Manager.
For this exercise, Transaction Manager will be configured to use the stored procedure dbo.getWIP to
check out the next manufacturing order from the database and directly update dbo.wipTrack when the
work at the current station has completed.
Click Step 4
Click the ellipsis [] button next to the Database Connection drop down box
Under the Server Name drop down box, select MI10
In the User Name field, enter fttm
In the Password field, enter fttm
Click Refresh
10 of 62
11 of 62
From the list of databases, select ProductionManagement and click Test
Click OK to acknowledge the Connection Succeeded message
Click Apply
Click OK on the Insert Success dialog then Close to return to the data object definition
window
Click the Stored Procedure radio button
12 of 62
From the Stored Procedure drop down box select dbo.getWIP
Click the >> button to select add all parameters to the data object.
13 of 62
In the Name field, enter MI10.ProductionManagement.dbo.getWIP
Click Apply
Click OK on the Insert Success dialog
Click the Table radio button
From the Table drop down box select dbo.wiptrack
Hold the Ctrl key and click on the fields, mfgorder, partID, and sta1out and click the >>
button to add these fields to the data object
Click the Update radio button
14 of 62
Right click on partID in the list of Data Object Columns and select Modify the update attribute
Click No
In the Name field, enter MI10.ProductionManagement.dbo.station1out
Click Apply to save changes and then Close to return to the configuration checklist
15 of 62
Connecting control system to database
With the connection to both the control system and database defined, the last step in building a
configuration is connecting control system points to database objects and determining when data
transfers should occur.
Click Step 5
From the Data Object Name select MI10.ProductionManagement.dbo.getWIP
Click the Enable radio button under the Transaction Status section
Right click on @station and select Bind Expression
16 of 62
In the Expression String field, enter station1 and click OK
Right click on @mfgOrder and select Separate Input/Output Parameter, do the same for
@partID. Note that there are now two entries for each parameter, an input labeled I and an
output labeled O
17 of 62
Right click on the input line of @mfgOrder and select Bind Null Value
Right click on the input line of @partID and select Bind Null Value
Right click on the output line of @mfgOrder and select Bind Data Point
Select FT.RSTechED2010._Devices::_MI10_Control_Station1.MfgOrder from the list of
available data points
Right click on the output line of @partID and select Bind Data Point
Select FT.RSTechED2010._Devices::_MI10_Control_Station1.partID form the list of available
data points
Check the box next to Bind Transaction Result
18 of 62
From the Bind Transaction Result drop down box select
FT.RSTechED2010::_MI10_Control_Station1.ReturnGetNext
Click the Trigger / Storage button
Click the On Unscheduled Event radio button
From the Unscheduled Event drop down box, select
FT.RSTechED2010::_MI10_Control_Station1.NextGet
Click OK to return to the transaction definition window
In the Transaction Name field enter Station1.IN
19 of 62
Click Apply
Click OK on the Insert Success dialog
From the Data Object Name drop down box, select
MI10.ProductionManagement.dbo.station1out
In the Transaction Name field, enter Station1.OUT
Right click on mfgorder and select Bind Data Point
Select FT.RSTechED2010._Devices::_MI10_Control_Station1.MfgOrder from the list of
available data points
Right click on partID and select Bind Data Point
Select FT.RSTechED2010._Devices::_MI10_Control_Station1.partID form the list of available
data points
Right click on sta1out and select Bind Expression
In the expression editor window, click the TransTimestamp() button
Click OK to return to the transaction definition window
Click Trigger / Storage
From the Unscheduled Event drop down box select
FT.RSTechED2010._Devices::_MI10_Control_Station1.BuildTimer.DN
Click OK to return to the transaction definition window
Check the box next to Bind Transaction Result
From the Bind Transaction Result drop down box, select
FT.RSTechED2010._Devices::_MI10_Control_Station1.ReturnStationOut
20 of 62
Click Apply
Click Yes on the Update Warning dialog.
Click OK on the Insert Success dialog
Click Close to return to the configuration checklist
Click Close to exit the configuration checklist
Testing the configuration
As with any system, the last step is test and validate.
From the Configuration menu select Start
21 of 62
22 of 62
Click Yes to confirm starting the configuration
From the View menu select Transaction Monitor
Launch the FactoryTalk View client from the desktop short cut
In the FactoryTalk View client, click the Get Next button
23 of 62
Note that in the FactoryTalk Transaction Manager window, Station1.IN reports 1 total and 1
passed transactions and the Ready to build indicator in FactoryTalk View is illuminated.
In the FactoryTalk View client, click the Build button
Note that when the build process completes, the FactoryTalk Transaction Manager window
Station1.OUT reports 1 total and 1 passed transactions and the Ready for next indicator in
FactoryTalk View is illuminated.
Open SQL Server Management Studio
24 of 62
Connect to the database engine on MI10 with Windows Authentication
Under MI10 > Databases > ProductionManagement > Tables, right click on dbo.wiptrack and
click Select Top 1000 Rows
25 of 62
Verify that the sta1in and sta1out fields for the manufacturing orders processed have updated
with the current date and time.
From the Configuration menu, select Stop
Click Yes to confirm stopping the configuration.
26 of 62
Exercise 2: Parameter Download / Recipe Management
A database makes the perfect repository for storing recipes or collections of build and test parameters for
products. Paired with a stored procedure and a small amount of control system logic, FactoryTalk
Transaction Manager can be used to transfer parameters from the database into the control system as
needed. This concept can be extended to allow a database to manage any type of data that is better
managed outside the control system and effectively makes a database an integral part of the control
system.
Exercise 2 builds on the previous configuration and pulls build parameters for a particular part and passes
it back to the control system.
Note if skipping exercise 1, restore C:\Lab Files\ex1complete.rsq to C:\Lab Files\MI10_Config\
as MI10_Config prior to starting this exercise.
Adding points to an existing configuration
Building upon the previous exercise the following additional controller tags are necessary to pull build
parameters from the database and send that information to the control system:
Controls the time required to build, and
/Devices::[MI10_Control]Station1.BuildTimer.PRE
example of a set point
Additional parameter example, not used in
/Devices::[MI10_Control]Station1.Parameters[0]
ladder in this lab.
Additional parameter example, not used in
/Devices::[MI10_Control]Station1.Parameters[1]
ladder in this lab.
Additional parameter example, not used in
/Devices::[MI10_Control]Station1.Parameters[2]
ladder in this lab.
Acknowledge that the parameters have been
/Devices::[MI10_Control]Station1.ReturnGetParam
downloaded successfully.
27 of 62
1. Right click on FT in the configuration tree and select Define Data Points
2. In the tag browser find and add the following tags:
/Devices::[MI10_Control]Station1.BuildTimer.PRE
/Devices::[MI10_Control]Station1.Parameters[0]
/Devices::[MI10_Control]Station1.Parameters[1]
/Devices::[MI10_Control]Station1.Parameters[2]
/Devices::[MI10_Control]Station1.ReturnGetParam
3. Change the mode of these new points to Device-Sched
28 of 62
4. In the tag browser add /Devices::[MI10_Control]Station1.PartID and change the mode to
Unsched
Note: Even though the PartID datapoint was already selected in exercise one, add the data point
again and change the mode of the newly created datapoint.
5. Click Apply to save changes and Close to return to the main window
29 of 62
Adding data objects to an existing configuration
6. Right click on OLEDB under OLEDB Connectors and select Define Data Object
7. From the Database Connection drop down box select \\MI10\ProductionManagement
8. Click the Stored Procedure radio button
9. From the Stored Procedure drop down box select dbo.getParam
10. Click the >> button to add all stored procedure parameters to the data object
30 of 62
11. In the Name field enter MI10.ProductionManagement.dbo.getParam
12. Click Apply to save changes and Close to return to the main window
Adding a transaction to an existing configuration
13. From the Define menu select Transaction
31 of 62
14. From the Data Object Name drop down box select
MI10.ProductionManagement.dbo.getParam
15. Right click on @p1 and select Separate Input/Output Parameter
16. Right click on the @p1 input parameter and select Bind Null Value
17. Repeat step 15 and 16 for @p2, @p3 and @p4
18. Right click on @partID and select Bind Data Point
32 of 62
19. Select Ft.RSTechED2010._Devices::_MI10_Control_Station1.PartID_1
20. Right click on the @p1 output parameter and select Filter & Select Data Points
21. Drag and drop Ft.RSTechED2010._Devices::_MI10_Control_Station1.BuildTimer.PRE onto the
@p1 output parameter
22. Drag and drop Parameters_0_ to @p2, Parameters_1_ to @p3 and Parameters_2_ to
@p4
23. Check the box next to Bind Transaction Result
33 of 62
24. From the Bind Transaction Result drop down box select
FT.RSTechED2010._Devices::_MI10_Control_Station1.ReturnGetParam
25. Click Trigger / Storage
26. Click the On Unscheduled Event radio button and select
FT.RSTechED2010._Devices::_MI10_Control_Station1.PartID_1 from the drop down box
27. Click the On Change radio button
28. Click the Ignore the First Unscheduled Event check box
29. Click OK to return to the Transaction Definition window
30. Click the Enable radio button
31. In the Transaction Name field, enter Station1.PARAM
32. Click Apply
33. Click OK on the Insert Success dialog then Close
34 of 62
Testing the modified configuration
34. From the Configuration menu select Start and click Yes to start the configuration
35. From the View menu select Transaction Monitor
36. Launch the FactoryTalk View client from the desktop short cut
37. Click on the indicator next to Bypass Recipe
38. In the FactoryTalk View client, click the Get Next button
35 of 62
39. Note that the parameter information updates and both the Station1.IN and Station1.PARAM
transactions have executed.
40. From the Configuration menu, select Stop
41. Click Yes to confirm stopping the configuration.
36 of 62
Exercise 3: Duplicating transactions
In many environments, a single FactoryTalk Transaction Manager instance is used to manage data flow
to several similar or identical areas of the plant. In such environments it is often desirable to create one
set of transactions and duplicate them for other identical areas of the plant.
Exercise 3 takes the work done in exercise 1 and 2 and shows how the XML import / export tool can be
used to rapidly deploy the same set of transactions for two additional areas.
Note if skipping exercise 1 and/or 2, restore C:\Lab Files\MI10_Config\ex2complete.rsq to C:\Lab
Files\MI10_Config\ as MI10_Config prior to starting this exercise.
Exporting existing configuration data
1. From the Tools menu select Wizards
2. Select the XML Import / Export Wizard radio button and click OK
3. Select the Export radio button and click Next
37 of 62
4. Under Export Settings uncheck Configuration Data and Connectors and click Next
5. Review the export summary and click Finish
38 of 62
6. Review the export results and click OK
Editing the exported file
7. Open SQL Server Management Studio
8. Connect to the database engine on MI10 with Windows Authentication
39 of 62
9. From the File menu, select Open>File
10. Open C:\Lab Files\MI10_Config\MI10_Config.xml
11. From the Edit menu, select Find and Replace > Quick Replace
40 of 62
12. In the Find and Replace window, under Find what: enter Station1 and under Replace with
enter Station2 and click Replace All
13. There should be 45 occurrences replaced. Click OK
14. Change Find what: to sta1 and Replace with: to sta2 and click Replace All
15. There should be 2 occurrences replaced. Click OK and close the Find and Replace"
16. From the File menu, select Save MI10_Config.xml As and change the file name to
Station2.xml
41 of 62
Importing new configuration data
17. In FactoryTalk Transaction Manager, from the Tools menu select Wizards and reopen the
XML import/export wizard
18. Select the Import radio button and click Next
19. From the Configuration drop down box select MI10_Config
42 of 62
20. Click the ellipsis button next to the XML File field and browse to C:\Lab
Files\MI10_Config\Station2.xml
21. Click Next
22. Review the summary and click Finish
23. When the import is complete, review the status and log. The import should complete with 16
successful and 4 failed records.
43 of 62
24. Click Open Log to view the import log. Note that the errors were for reused objects and not new
objects.
25. In FactoryTalk Transaction Manager, click on a different entry in the configuration tree to force a
refresh. Note: a second set of transactions have been created
26. Repeat steps 12 thru 25 for Station 3.
27. Start the configuration and test each station as documented in exercise 1 and 2.
28. From the Configuration menu, select Stop
29. Click Yes to confirm stopping the configuration.
44 of 62
Exercise 4: Buffered data collection
While useful for bi-directional data management, the most common application for FactoryTalk
Transaction Manager is data collection. While simple data point reads and table inserts are enough for
most applications, some data collection scenarios require the control system to buffer data to be collected
in short bursts.
Exercise 4 walks through an example buffered data collection scenario and illustrates additional import /
export tools that can be used to augment the user interface and allow for rapid development of
applications.
Note if skipping previous exercises, restore C:\Lab Files\MI10_Config\ex3complete.rsq to C:\Lab
Files\MI10_Config\ as MI10_Config prior to starting this exercise.
Duplicating points with Excel
1. Right click on FT in the configuration tree and select Define Data Points
2. In the tag browser find and add the following tags:
/Devices::[MI10_Control]Buffer[0].DateTime
/Devices::[MI10_Control]Buffer[0].Value
/Devices::[MI10_Control]BufferResult
/Devices::[MI10_Control]BufferIndex
3. Change the mode of Buffer[0].DateTime, Buffer[0].Value and BufferResult to Device-Sched and
BufferIndex to Unsched
45 of 62
4. Select the row for /Device::[MI10_Control]Buffer[0].DateTime and press CTRL-C
5. Open Microsoft Excel and create a new workbook and press CTRL-V to paste
6. In Column A, add an equal sign and double quote at the start of the line and a double quote at the
end.
7. Replace the 0 in Buffer[0] with &ROW()-1& including the quotation marks as shown
8. In column B, add an equal sign and double quote at the start of the line and a double quote at the
end.
46 of 62
9. Replace the 0 in Buffer_0_ with &ROW()-1& including the quotation marks as shown
10. Note that the display values in columns A and B are still the same as in the Data Point Definition
window in FactoryTalk Transaction Manager.
11. Select the row and drag the copy/fill handle down 20 rows
12. Excel may perform a Fill Series by default, ensure that it performs a copy by clicking on the
popup menu and selecting Copy Cells
47 of 62
13. Delete columns N and O from the spreadsheet
14. Press Ctrl-A to select all and Ctrl-C to copy
15. Click on an empty line in the data point definition window in FactoryTalk Transaction Manager
and press Ctrl-V to paste.
16. In the Data point name resolution message, click Modify Existing
17. Repeat steps 4-16 on a new sheet in the same workbook for
/Devices::[MI10_Control]Buffer[0].Value. Leave Microsoft Excel open when complete
18. In FactoryTalk Transaction Manager, click Apply to save changes and then Close
48 of 62
Adding a new data object
19. Right click on OLEDB under OLEDB Connectors and select Define Data Object
20. From the Database Connection drop down box select \\MI10\ProductionManagement
21. Click the Stored Procedure radio button
22. From the Stored Procedure drop down box select dbo.storeBuffer
23. Click the >> button to add all stored procedure parameters to the data object
49 of 62
24. In the Name field enter MI10.ProductionManagement.dbo.storeBuffer
25. Click Apply to save changes, and OK on the Insert Success dialog
26. Click Close to return to the main window.
Exporting a transaction template
27. From the Define menu, select Transaction
28. In the Transaction Name field, enter StoreBuffer
29. From the Data Object Name drop down box select
MI10.ProductionManagement.dbo.storeBuffer
30. Click Apply to save the transaction in a partially configured state.
31. Click OK to acknowledge the pointless transaction error
50 of 62
32. Click Yes to save the transaction with errors
33. Click OK on the Insert Success dialog and Close to return to the main window
34. From the Tools menu. Select Wizards
35. Select Transaction Import/Export Wizard and click OK
36. Click Next
51 of 62
37. Select Export Transaction, enter My Documents\StoreBuffer.tsv and click Next
38. From the Data Object drop down box select MI10.ProductionManagement.dbo.storeBuffer
52 of 62
39. Check StoreBuffer and click Finish
40. The wizard will report an error, click Finish to restart the wizard.
41. Leave the wizard window open and go back to Microsoft Excel
Building a transaction in Excel
42. Open the My Documents\storeBuffer.tsv in Microsoft Excel
43. When the file opens, Microsoft Excel will display a text import wizard. Click Finish to close the
wizard.
44. In Row 2, Column A enter StoreBuffer
53 of 62
45. From the original workbook, copy the contents of column B on the sheet used to create the
.DateTime data points. Note: Do not select the entire column. Only select the cells with data
from rows one through twenty.
54 of 62
46. In StoreBuffer.tsv, select Row 2, Column D, right click and select and Paste Special
47. In the Paste Special dialog, select Values and check the Transpose checkbox then click OK
55 of 62
48. From the original workbook, copy the contents of column B on the sheet used to create the
.Value data points. Note: Again, do not select the entire column. Only select the data in the
cells from row one through twenty.
56 of 62
49. In StoreBuffer.tsv, select Row 2, Column X, right click and select Past Special
50. In the Paste Special dialog, select Values and check the Transpose checkbox then click OK
51. Save StoreBuffer.tsv and close the file.
Importing a nearly complete transaction
52. Return to the Transaction import / export wizard and click Next
53. In the File Name field enter My Documents\StoreBuffer.tsv and click Next
54. Click Next on the Import Confirmation screen to perform the import and OK when the import
has completed.
55. Close the transaction Import/Export wizard.
57 of 62
Completing the imported transaction
56. In FactoryTalk Transaction Manager window, from the Define menu, select Transaction
57. From the Transaction Name drop down box, select StoreBuffer
58. Right click on @tagName and select Bind Expression
59. Click the String button and type Tag1 then click OK
60. Check the Bind Transaction Result checkbox and select
FT.RSTechED2010_Devices::_MI10_Control_BufferResult
61. Click Trigger / Storage
62. Select On Unscheduled Event and select
FT.RSTechED2010_Devices::_MI10_Control_bufferIndex from the drop down box.
58 of 62
63. Select On Change and Click OK
64. Click Apply and the Close to return to the main window.
65. From the Configuration menu, select Start
66. From the View menu, ensure that Transaction Defnition is selected.
67. Right click on StoreBuffer and select Enable Transaction
59 of 62
68. Click the Assemble All button on the toolbar
69. Click Yes accept the pending edits and OK to acknowledge that edits have been assembled.
70. From the View menu, select Transaction Monitor and note that StoreBuffer is now triggering
and collecting data
71. From the Configuration menu select Stop and stop the configuration.
Open SQL Server Management Studio
Connect to the database engine on MI10 with Windows Authentication
60 of 62
72. Under MI10 > Databases > ProductionManagement > Tables, right click on dbo.sampleBuffered
and click Select Top 1000 Rows
61 of 62
73. Verify that the table contains data collected from the controller.
Conclusion
The exercises in this lab demonstrate a subset of the data management applications possible with
FactoryTalk Transaction Manager. From simple data logging to complex manufacturing intelligence
applications, FactoryTalk Transaction Manager can be used to manage the flow of information from the
control system to the enterprise.
62 of 62
