SY16 - Become a Superhero with

FactoryTalk® AssetCentre's
Advanced System Features

c
 Important User Information
This documentation, whether, illustrative, printed, “online” or electronic (hereinafter “Documentation”) is intended for use only as
a learning aid when using Rockwell Automation approved demonstration hardware, software and firmware. The Documentation
should only be used as a learning tool by qualified professionals.

The variety of uses for the hardware, software and firmware (hereinafter “Products”) described in this Documentation, mandates
that those responsible for the application and use of those Products must satisfy themselves that all necessary steps have been
taken to ensure that each application and actual use meets all performance and safety requirements, including any applicable
laws, regulations, codes and standards in addition to any applicable technical documents.

In no event will Rockwell Automation, Inc., or any of its affiliate or subsidiary companies (hereinafter “Rockwell Automation”) be
responsible or liable for any indirect or consequential damages resulting from the use or application of the Products described in
this Documentation. Rockwell Automation does not assume responsibility or liability for damages of any kind based on the
alleged use of, or reliance on, this Documentation.

No patent liability is assumed by Rockwell Automation with respect to use of information, circuits, equipment, or software
described in the Documentation.

Except as specifically agreed in writing as part of a maintenance or support contract, equipment users are responsible for:
• properly using, calibrating, operating, monitoring and maintaining all Products consistent with all Rockwell Automation
or third-party provided instructions, warnings, recommendations and documentation;
• ensuring that only properly trained personnel use, operate and maintain the Products at all times;
• staying informed of all Product updates and alerts and implementing all updates and fixes; and
• all other factors affecting the Products that are outside of the direct control of Rockwell Automation.

Reproduction of the contents of the Documentation, in whole or in part, without written permission of Rockwell Automation is
prohibited.

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

Identifies information about practices or circumstances

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

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

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

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

Labels may be located on or inside the drive to alert people that surfaces may be dangerous temperatures.
Become a Superhero with FactoryTalk® AssetCentre's Advanced System Features

Contents
Before you begin ........................................................................................................................................... 5
About this lab .................................................................................................................................................................................... 5
Software ............................................................................................................................................................................................ 5
Lab files............................................................................................................................................................................................. 5
Advanced Section ............................................................................................................................................................................. 5
Virtual Machines and lab domains .................................................................................................................................................... 6
User and Passwords ......................................................................................................................................................................... 6

What’s New in FactoryTalk AssetCentre 9.00? ............................................................................................ 7

Section 01: Simplifying Configuration with the Import/Export Utility (25-30 minutes) .................................. 8

Section 02: Configuring Asset Inventory Scans & Lifecycle Management (20-25 minutes) ........................ 9
Creating a new Asset Inventory asset ............................................................................................................................................ 10
Scan for Assets ............................................................................................................................................................................... 12
Review Asset Inventory Scan Results ............................................................................................................................................ 14
Add assets from the scanning result to the asset tree .................................................................................................................... 16
Update assets on the asset tree with new asset properties............................................................................................................ 22
Viewing Asset Lifecycle Status ....................................................................................................................................................... 26

Section 03: Disaster Recovery for FactoryTalk View Site Edition Application (25-30 minutes) ................ 36
Launching FactoryTalk AssetCentre ............................................................................................................................................... 36
Create a FactoryTalk View Site Edition Asset ................................................................................................................................ 37
Verify existing Schedule.................................................................................................................................................................. 40
Execute a Schedule to Create a Backup ........................................................................................................................................ 41
Make Changes to the Application ................................................................................................................................................... 43
Execute a Schedule ........................................................................................................................................................................ 45
Recovering Application Changes .................................................................................................................................................... 49
BONUS! FactoryTalk AssetCentre and FactoryTalk View SE TrendPro Integration ..................................................................... 54

Section 04: Managing AssetCentre Database Size (25-30 minutes) ........................................................ 57

Configuring Database Limitations ................................................................................................................................................... 57

3 of 132
Create Archive Cleanup Configuration File..................................................................................................................................... 60
Execute Archive Cleanup Utility from Command Line .................................................................................................................... 65
View Archive Clean-up Utility Results ............................................................................................................................................. 67
Diagnostic Log Cleanup Wizard...................................................................................................................................................... 69
Configuring Log Cleanup from Command Line............................................................................................................................... 72
Execute Log Cleanup from Command Line .................................................................................................................................... 74
View Purged Log data..................................................................................................................................................................... 76
Configuring Database Limitations (again) ....................................................................................................................................... 77

Section 05: Securing FactoryTalk AssetCentre (15-20 minutes) ............................................................... 79

Launching FactoryTalk AssetCentre ............................................................................................................................................... 79
Creating new Users and Groups..................................................................................................................................................... 80
Securing AssetCentre functions (Design Mode) ............................................................................................................................. 86
Securing the FactoryTalk AssetCentre Asset Tree ......................................................................................................................... 88
Exercise Security Configuration ...................................................................................................................................................... 91

Section 06: Disaster Recovery for ControlLogix (15-20 minutes) .............................................................. 93

Retrieve ACD File ........................................................................................................................................................................... 93
Configure Logix 5000 Asset ............................................................................................................................................................ 96
Configure ControlLogix Disaster Recovery ................................................................................................................................... 102
Execute ControlLogix Disaster Recovery Task............................................................................................................................. 106

Section 07: Using Custom Device Disaster Recovery with 3rd-Party Scripting Tool (20-25 minutes) .... 109
Custom Device Configuration ....................................................................................................................................................... 109
Create Custom Device Asset ........................................................................................................................................................ 118
Execute Custom Device Disaster Recovery Task ........................................................................................................................ 123

Section 08: Stratix Switch Archive to Archive Comparison (10-15 minutes) ........................................... 128
Launching FactoryTalk AssetCentre ............................................................................................................................................. 128
Archive to Archive Compare – Archive Only ................................................................................................................................. 129

4 of 132
Before you begin

About this lab

Welcome to the Hands-On Lab for FactoryTalk AssetCentre Advanced Configuration. This lab is organized into eight main
sections, each with an estimated time to completion. These sections need not be completed sequentially, and many users will
not complete the entire lab. Please select the most interesting sections to complete first.

Software
This Hands-On Lab uses the following software:
 Microsoft Windows Server 2016 Standard
 FactoryTalk AssetCentre v9.00
 Studio 5000 Logix Designer v21.03 and v32.00
 FactoryTalk View SE and ME v11.0
 RSLogix Emulate 5000 v21.03
 Microsoft SQL 2016 Standard
 AutoIt Scripting Language Open Source Tool v3.3.14.5

Lab files
This Hands-On Lab uses the following files:
 Contents of C:\Lab Files\
 Contents of C:\AutoIt\

Advanced Section
The Advanced section is a collection of advanced topics. As you complete the advanced section in this hands-on session, you
will:
 Explore the FactoryTalk AssetCentre Import Export Utility, and learn how it can reduce design and maintenance time
 Manage the system’s asset inventory and view lifecycle information, using the Asset Inventory agent
 Configure a new FactoryTalk View Site Edition asset, including Disaster Recovery functionality
 Learn how to manage database growth in a FactoryTalk AssetCentre system
 Secure a FactoryTalk AssetCentre system
 Configure a new ControlLogix asset, including Disaster Recovery functionality
 Learn about Custom Devices in FactoryTalk AssetCentre, and how to use them with a 3 rd-party scripting tool
 Explore the Archive to Archive compare functionality using the Stratix Switch archived files

5 of 132
Virtual Machines and lab domains
The virtual machine is set up as follows:

Machine description Machine name Operating system

FactoryTalk AssetCentre System FTAC-DEMO19 Windows Server 2016 Standard

FactoryTalk AssetCentre does not require a domain; this lab is conducted in a Windows workgroup named WORKGROUP.

User and Passwords

Following are the Windows user logins and passwords that may be used in the lab:

Login Password Full user name Group / user type

administrator rockwell System Administrator Windows Administrator

FactoryTalk Administrators

labuser rockwell System Administrator Windows Administrator

FactoryTalk Administrators

FactoryTalk Security’s single sign-on feature has been enabled as part of this lab. This means that FactoryTalk Security will
automatically use your operating system login to authenticate your security rights in FactoryTalk AssetCentre. Should you need
to manually log into FactoryTalk AssetCentre, we will use the same log-in credentials (see above).

6 of 132
What’s New in FactoryTalk AssetCentre 9.00?

The new functionality introduced in version 9.00 of FactoryTalk AssetCentre falls into these main groups:

 Disaster Recovery for FactoryTalk View Site Edition Applications: A FT View SE asset is now
available for Disaster Recovery operations. The FT View SE asset is capable of backing up the entire FT
View SE application including the HMI server, FT Directory, FT Linx, and FT Alarms & Events.
 Disaster Recovery for Stratix Switches: A Stratix Switch asset is now available for Disaster Recovery
operations. The Stratix Switch asset is capable of backing up the switch data including the configuration file
(config.txt), the VLAN file (vlan.dat), and the DLR file (dlr.dat) via Telnet or SSH.
 Secured Communications: FactoryTalk AssetCentre is supported in a network security architecture based
on Internet Protocol Security (IPSec). FactoryTalk AssetCentre adopts FactoryTalk Linx Enterprise allowing
Disaster Recovery operations of devices that are members of a secured zones.
 Controller IO Lifecycle: IO modules of a FactoryTalk AssetCentre asset can be associated to the
controller to obtain IO lifecycle information synchronized with the Product Compatibility and Download
Center. The IO can manually be entered or automatically retrieved from the ACD file.
 Asset Extended Properties: FactoryTalk AssetCentre assets can be customized with extended properties
to store and associate information-specific to an asset, which includes up to 20 properties. Asset extended
property information can be used for ad-hoc or scheduled Search reporting.
 Diagnostics Connector: Diagnostic information can be collected from computers that are part of the FT
Directory where AssetCentre is configured without having to install the AssetCentre client.

7 of 132
Section 01: Simplifying Configuration with the Import/Export Utility (25-30 minutes)

As of version 8, the Import/Export utility allows for multiple options of importing and exporting the asset tree. Users
can select full and partial exports, as well as automated asset creation. Assets can be edited in an application like
Microsoft Excel by exporting to CSV formatting, then propagating the edits into AssetCentre with an import.

Important: Please read!

Section 01 “Simplifying Configuration with the Import/Export Utility” was removed due to Microsoft licensing not being
supported in the Azure environment

Please refer to the “Using the FactoryTalk AssetCentre Import Export Utility” video on the Rockwell Automation
YouTube channel (https://www.youtube.com/user/ROKAutomation) to view the new Import/Export tool introduced in
version 8.00 of FactoryTalk AssetCentre.

8 of 132
Section 02: Configuring Asset Inventory Scans & Lifecycle Management (20-25 minutes)

The Asset Inventory asset allows you to have an overview of physical devices on the network and sync them to the
asset tree accordingly. By running a backup or backup and compare schedule on an Asset Inventory asset, the
Asset Inventory agent service scans the connected devices and computers on the network and stores unique
identification information about hardware, firmware, and software in the backup data. You can open the backup data
in the Asset Inventory window, which shows the scanning result of devices and associated software in grid view.
With Asset Inventory, you can:
 View the detailed scanning result of device assets on the network and associated software
 Add new assets from the scanning result to the asset tree
 Update assets on the asset tree with new asset properties
 Export the scanning result for further analysis

The list of assets – both in the asset tree, as well as the results of an Asset Inventory scan, can also be used to
display asset lifecycle status. The Assets Lifecycle functionality allows the AssetCentre Client to display the lifecycle
for a set of assets. Users can view lifecycle status based on the Asset Tree hierarchy, or an RAAI file from a CIP
Inventory Scan. The lifecycle status is synchronized online with the Product Compatibility and Download Center.
The following Lifecycles can be displayed:

Status Description
None Indicates the life-cycle status is not available for the asset.
Active Most current offering within a product category.
Active Product is fully supported, but a newer product or family exists. Gain value by
Mature migrating.
Discontinued date announced - actively execute migrations and last time buys.
End of Life
Product generally orderable until the discontinued date.
New product no longer manufactured or procured. Repair/exchange services may
Discontinued
be available.

9 of 132
Creating a new Asset Inventory asset
An Asset Inventory asset can be configured to scan for assets using RSLinx Classic (CIP Scanning), SNMP (e.g.,
network switches), and WMI (used to create Windows installation inventories). A single asset can be used for all
three types of scanning, or any subset. In this section of the lab, you will learn how to create a new Asset Inventory
asset, and configure it to scan the RSLinx Classic configuration.

1. Open the FactoryTalk AssetCentre Client from the Start menu.

2. Click the Design button.

3. From the asset tree, navigate to AssetCentre  Plant Layout  Asset Inventory

4. Add a new Asset Inventory asset to the container.

10 of 132
5. Click the browse button next to the Scanning Configuration

Note: No Backup Data file is needed for the Asset Inventory asset. This file is created during the first
run of the Backup or Backup and Compare schedule configured for the Asset Inventory Asset.

6. In the Scanning Configuration dialog box, select the Scan devices using CIP checkbox and click the browse
button next to Start scanning with this device.

7. From the Select Device for Asset Type: “Asset Inventory” window, select the AB_VBP-1, 1789-A17/A Virtual
Chassis and click Select.

Note: The Advanced Settings button provides adjustable timeout values to assist in adjusting the scan
for network performance.

8. Click OK to confirm the Scanning Configuration, and OK again to close the asset properties.

11 of 132
Scan for Assets
Once an Asset Inventory asset is configured, it must be scheduled. Scheduling the asset as part of a Disaster
Recovery task will trigger the scan at scheduled intervals. The scan will produce an RAAI file containing the resulting
asset inventory, which can also be compared against previous scheduled runs for differences.
1. Click the Schedules tab.
2. With the Asset Inventory asset selected in the Asset Tree, click the New… button in the Schedules tab.

3. Select a Disaster Recovery – Backup and Compare schedule, and name it Asset Inventory Scan.

4. Click Next.
5. Accept the defaults for the Timing Properties and click Next.
6. Change the Create New Backup Version property from Always to On Difference Found.

Note: By default, a new RAAI file will be added to the archive after each scan. On Differences
Found will only add a new version to the archive if it is different from the previous version.

7. Click Finished and click Yes to save the changes.

12 of 132
8. With the Asset Inventory Scan schedule selected, click Run Now.

9. The schedule will take approximately 30 seconds to complete. Monitor the task status until you see “Operation
Succeeded”

Notice the new RAAI file in the asset tree, automatically added by the schedule.

13 of 132
Review Asset Inventory Scan Results
An Asset Inventory scan returns its results in an RAAI file, associated with the asset as the Backup Configuration.
The RAAI file can be viewed directly within the FactoryTalk AssetCentre client.

1. Right click the Asset Inventory_Backup.raai file from the Asset Tree and select Open.

2. Confirm that the Show in Asset Inventory Grid View checkbox is checked, then click Checkout.

3. Click OK.

14 of 132
4. Notice the total asset count in the bottom right of the window. Click the button to maximize the Asset
Inventory window.

Note: The Asset Inventory window is a modal display. This means that the FactoryTalk AssetCentre
user is not able to switch back and forth between the FactoryTalk AssetCentre Client and the Asset
Inventory Grid View program.

5. View all discovered by clicking Expand All

6. You should now be able to easily read the Devices discovered, including its product type and firmware revision.
7. When you’re done exploring the RAAI file, close the viewing window to return to the FactoryTalk AssetCentre
client.

In this lab, the emulated controller is the only available device to scan. It’s not too interesting to look at scan results
and lifecycle status of emulators, though. Now that you’ve learned the basics of how Asset Inventory assets work,
we’ll start working with an RAAI file from a physical environment.

15 of 132
Add assets from the scanning result to the asset tree
With an asset inventory scan completed, you can use the results to maintain your asset tree. In this section of the
lab, you’ll see how to add a new asset directly from an RAAI file.

1. From the Asset Tree, navigate to AssetCentre  Plant Layout  Asset Inventory  Example Inventory.
Right click on Example.raai file and select Open.

2. Click Check Out and OK.

3. Click the button to maximize the Asset Inventory window.

4. Click Expand All to display all information from the scan.

16 of 132
5. With the Add radio button selected, click the SYNC button.

Warning: If the FactoryTalk AssetCentre Client is not in Design Mode, the Add / Update action is not
possible. If you receive the following warning, return to the FactoryTalk AssetCentre Client, click
Design and return to step one.

6. During the SYNC process, the Asset Inventory Grid View program is checking the results of the scan with the
devices in the AssetCentre Asset Tree.

When the SYNC process completes, scroll down, and you’ll see two assets are grayed out. Notice the Existing
Devices count in the bottom right of the window. The SYNC has discovered that these assets are already part
of the asset tree, so it cannot be added again.

17 of 132
7. Let’s add the other module in that chassis! As you can see, the results of a scan can have many devices. Let’s
take advantage of the Search action.
8. From the RAAI file, click Search from the action bar to search for a specific device.

9. From the Search for Asset Inventory window, scroll down, and under the Field column, select the Product Name
and Revision checkboxes. Notice the value of the Compare Operator column. This value allows you to search
for a string that contains the compare value.
Under the Compare Value column, enter L75 for Product Name and 21 for Revision, click Search.

10. Now you can see all the 1756-L75 controllers that are revision 21.11. Select the first L75 from the search results
and check its checkbox.

18 of 132
11. Click Add from the action bar to proceed with adding this new device to the Asset Tree.

12. Notice the asset type is automatically identified. All we have to do is give it a name and location in the asset
tree!

13. Name the new asset Batch2_CLX and locate it in AssetCentre/Plant Layout/Process Area and click Next.

14. Click Start.

19 of 132
15. When complete, you will see a results window, and the asset will turn gray in the RAAI file.

16. Click Finish, then close the RAAI file.

17. The new asset is now part of the asset tree! If you open its properties, you will see everything but the
Configuration Data configured!

18. Let’s finish the asset configuration by adding the controller ACD file under Configuration Data.

20 of 132
19. Locate the controller ACD file under AssetCentre/Files/Studio 5000 and select the Projects folder. Select
Batch2_CLX.ACD file, and click OK.

20. Click OK.

21. Your new asset is configured!

21 of 132
Update assets on the asset tree with new asset properties
In this section of the lab, you will use the results of an Asset Inventory scan to update a linked asset in the asset tree.
This example will walk through how to update the Firmware Revision property.
1. Open the properties for the Batch_CLX asset located at AssetCentre  Plant Layout  Process Area.

This asset was added to the asset tree, then its firmware version was updated. AssetCentre does not
automatically update this property, but you can keep your assets up to date using the Asset Inventory scan.
2. Click Cancel to close the properties window.
3. From the Asset Tree, right click on the Example.raai file, and select Open. The file will launch automatically.
If prompted with the Asset Retrieval Options, select Get.

4. Click the button to maximize the Asset Inventory window.

22 of 132
5. Click Expand All to display all information from the scan.

6. With the Update radio button selected, click the SYNC button.

7. Scroll down, and you’ll notice that most of the content is grayed out. Notice the Devices Available for Update
in the bottom right of the window.

8. The Update function only applies to assets that are already part of the asset tree.
9. If the asset is matched to one in the asset tree, the SYNC process then determines if there are any differences in
the properties. Because we just added the lower asset in the last section, all of its properties are up to date.
The Batch_CLX asset, however, shows the firmware difference:

Scroll down and notice the second asset that is available for update. For the next exercise, we will only be
updating the controller. Uncheck the Stratix switch.

23 of 132
10. Click Update.

11. Notice the confirmation window.

12. Click Start.

13. Notice the successful result. Click Finish.

14. Close the RAAI file.

24 of 132
15. Open the properties for Batch_CLX from the asset tree.

The firmware version has been updated!

16. Click Cancel to close the properties window.

17. Click Design to exit Design Mode.

25 of 132
Viewing Asset Lifecycle Status
In this section of the lab, you will use the Assets Lifecycle view to display the lifecycle of the assets defined in the
FactoryTalk AssetCentre asset tree.

1. Click the Assets Lifecycle button to open the view.

2. The Assets Lifecycle view opens

Sync: This button will synchronize the FactoryTalk AssetCentre database with the Product
Compatibility and Download Center lifecycle database, ensuring current information in the local
system. Requires an internet connection.
Refresh: This button causes the client view to refresh, using the lifecycle information stored in the
local database. No internet connection is required for this operation.
Export: The Lifecycle information can be exported to CSV or TXT formats.
Asset / Asset Inventory: The Assets view shows the lifecycle information of the assets
configured in the Asset Tree. The Asset Inventory view displays lifecycle information for the
results of a CIP Inventory Scan.

26 of 132
3. In the Assets Lifecycle windows, expand AssetCentre  Plant Layout  Process Area. Notice the lifecycle
displayed on multiple assets, but not on Generic Containers. Only an asset can have an associated Lifecycle:

The Lifecycle status is matched to the Catalog Information of an asset. Assets such as a
ControlLogix module will automatically populate the asset’s Catalog Information.

The indicator shows an asset for which no Lifecycle status is available. Assets such as
an Asset Inventory scan and a Custom Device do not have a corresponding Catalog Information
property, so these assets will always show .

27 of 132
4. Click on Batch_CLX and Batch2_CLX to view more information on its status. Notice that the Last Update Date
field might be different. This field determines the last time the AssetCentre database was synchronized with the
Product Compatibility and Download Center website to obtain lifecycle information.

Note: The information panel shows the asset’s path within the asset tree, the date the catalog
number was discontinued (if applicable), and a functional replacement (if applicable). The Last
Update Date shows when AssetCentre last updated this catalog number from the Product
Compatibility and Download Center.

5. What about the IO associated to the process area controllers? Let’s take advantage of the asset Controller IO
property to obtain IO lifecycle.
6. Click Design to enter Design Mode.

28 of 132
7. From the Asset tree, navigate to AssetCentre  Plant Layout  Process Area, and select the newly added
Batch2_CLX asset.
Right click on the asset and select Properties.

8. Notice the Controller IO property. Select to open the window properties.

There two ways to associate IO to a controller. You can manually enter the IO Name, Catalog
Number, Major Revision, and Minor Revision, or you select the Overwrite with Current ACD to
automatically retrieve and populate the field(s) with the IO defined in the archived ACD file (lasted
archived version or pinned version).

9. Select Overwrite with Current ACD to automatically retrieve the IO information from the controller ACD file and
populate the fields with the current IO information.
10. Select OK in the confirmation window.
11. Notice the progress bar. It will take approximately 10 seconds.

29 of 132
12. You can see that the IO has been automatically populated. Notice the Name values. This are the names that
are given to the IO module in the controller file.

13. Let’s change the name of one of the IO modules.

14. Select the last module myDigitalIn and double click it to change the name. Change the name to S06 1756-
IB16. This action will not affect the controller file.

15. Click OK to close the Controller IO properties window.

16. Click OK to close the Batch2_CLX asset properties.

30 of 132
17. Go back to the Assets Lifecycle plug-in. Under the Asset view, expand the Batch2_CLX asset and notice that
some of the IO was automatically added with the correspondent lifecycle status.

The Asset Lifecycle information will be automatically populated if the information already exists
within the AssetCentre database. This information is available due to previous synchronization
with the Product Compatibility and Download Center website.

18. Clink on the Batch2_CLX lifecycle status and look at the Last Update Date. This field indicates the last time
the AssetCentre database was synchronized with the Product Compatibility and Download Center website to
obtain lifecycle information.

19. Let’s synchronize with the Product Compatibility and Download Center website. Select Sync.

As previously mentioned, a Sync action requires internet access.

31 of 132
20. Once the Sync operation is complete, click on the Batch2_CLX lifecycle status. Notice that the asset has been
updated with the latest lifecycle information (current date). Feel free to review the other assets lifecycle
statuses.

21. Click on Asset Inventory.

Note: The Asset Inventory view displays Lifecycle status based on the scan results of an Asset
Inventory CIP scan (RAAI file). An Asset Inventory scan can return results that are not necessarily
referenced in the Asset Tree (for example, an Input module), so the Asset Inventory view can give
a more comprehensive list of the assets in a system.

22. Notice the browse button . This allows you to select and view different Asset Inventory CIP scan results.

32 of 132
 If no RAAI is present. Select the browse buton . Navigate to AssetCentre  Plant Layout  Asset
Inventory  Example.raai and click OK.

Note: Each FactoryTalk AssetCentre client’s RAAI file selection can be different; this is not a
global setting.

23. Explore the Asset Inventory view. Click the SYNC button to synchronize with the PCDC site. You can see
multiple examples of lifecycle statuses.

33 of 132
24. Let’s check for any Discontinued statuses. Click the By Status drop down, then select Discontinued.

25. Notice that there are several assets shown whose status is not Discontinued. These are parent assets who
have at least one child asset that shows as Discontinued.

26. Click on the first 1756-EN2TR asset to bring up its Discontinued status information.

An asset with a discontinued status will show the discontinued date, as well as the functional replacement!

34 of 132
 Important: Please read!
The following steps are for information purposes. DO NOT export to CSV due to Microsoft licensing not
being supported in the Azure environment.

27. The entire RAAI view can also be exported. Use the Export button to save a CSV to the Desktop.

28. Save the exported CSV to the desktop.

29. Open the CSV, and you’ll find the full list of assets and their respective lifecycle status

30. When finished, close the CSV file.

In this section of the lab, you’ve learned how to configure an automated inventory scan, how to correlate scan results
back to the asset tree, and how to view your assets’ lifecycle status!

35 of 132
Section 03: Disaster Recovery for FactoryTalk View Site Edition Application (25-30 minutes)

In this section of the lab, you will work with a new asset type called FactoryTalk View Site Edition. Using the
FactoryTalk View Site Edition asset, you can automatically back up and compare the entire FactoryTalk View Site
Edition application including the HMI server, FactoryTalk Directory, FactoryTalk Linx, FactoryTalk Alarms & Events
during production. The selection is backed up and archived as an APB file extension. The APB file extension is
used by the FactoryTalk View SE Application Manager utility to manage SE applications such as renaming, deleting,
backing up, and restoring.
In this section, you will be configuring a FactoryTalk View Site Edition asset to back up and compare the InstantFizz
application. When completed, you will be able to restore a display from the archived version without having to check
out the entire application.

Launching FactoryTalk AssetCentre

In this section you will launch the FactoryTalk AssetCentre Client, if it’s not already open.

1. From the Start menu select AssetCentre Client. You can also double-click the FactoryTalk AssetCentre Client
icon on the desktop:

36 of 132
Create a FactoryTalk View Site Edition Asset

1. Click the Design button to enter design mode.

2. Navigate to AssetCentre → Plant Layout → FT View SE Application.

3. In the Device Items Catalog, select FactoryTalk View Site Edition and Click the Add FactoryTalk View Site
Edition to FT View SE Application button.

4. Enter the name ViewSE_App.

37 of 132
5. Select the Backup Configuration property and click the browse button to connect to the FactoryTalk
Network Directory and select the application to be backed up. Note that assigning the Backup Data property is
not necessary, as one will be created upon the first execution of the Disaster Recovery Task.

6. Enter the labuser credentials and click Connect. Once access is granted, select the InstantFizz application
which will be backing up in this example, and click OK.

Username: labuser

Password: rockwell
User access to the FactoryTalk
Network Directory is required to back
up the FactoryTalk View Site Edition
application. At a minimum, the user
must have Read and Execute
permissions. FactoryTalk user and
Windows user (local or domain) are
supported.

The user can choose to encrypt the

application backup file. Note that
this password will be required when
restoring the application using the
FactoryTalk View SE Application
Manager utility.

FactoryTalk AssetCentre can only backup FactoryTalk View Site Edition applications that are part
of the same FactoryTalk Network Directory, and it can only backup one application per FactoryTalk
View Site Edition asset.

38 of 132
7. The asset configuration is complete! Click OK to continue.

8. Click the Design button to exit design mode.

9. With the new FactoryTalk View Site Edition asset configured, let’s run a Disaster Recovery Schedule.

39 of 132
Verify existing Schedule

1. Click the button to start the Schedules plug-in.

2. Select the Weekly schedule.

3. Click the View By Asset Type; notice that our ViewSE_App asset was automatically added to this schedule.

When the schedule was originally created, it was created at the highest level in the Asset View ,
this can been seen by viewing the Schedule Location property. All content of the node at which the schedule is
created will be available for the schedule dynamically, even if more assets are added after the schedule was
created.

Note: You can create schedules at any level in the Asset View. The Scheduler will by default add
any assets to that schedule which supports Disaster Recovery at or below that level. To remove
an asset simply uncheck that asset.

4. For our lab purposes uncheck the Batch2_CLX, Asset Inventory, and any other assets that are currently
enabled. Your screen should look like the following:

40 of 132
Execute a Schedule to Create a Backup
1. Set focus back to the ViewSE_App asset and notice the Disaster Recovery task properties, specifically the
2.Asset specific properties.

Compare Options: Set which parts of an application to get compared following an upload.
Create New Backup Version Due to Unmatched Passwords: Determines whether to create a
new backup version when the archived version encrypted password is different from the new
backup version.
Include Data Log: Determines whether to include the data log files (MDF) when backing up the
application. Database size must be considered when setting this option to True.

2. Click the Run Now button in the Scheduling toolbar to execute the schedule. The Status column
should update to show a Running state for the schedule you created.

41 of 132
3. Once the task is complete, notice that a new backup file has been added to the ViewSE_App you created.

4. Let’s minimize FactoryTalk AssetCentre Client for now.

42 of 132
Make Changes to the Application

In this part of the lab, we are going to make changes to the InstantFizz application. We will then run a Backup and
Compare operation using our existing Schedule to back up and report these differences.

1. From the Start menu select FactoryTalk View Studio. You can also double-click the FactoryTalk View Studio
icon on the desktop:

2. Under Application Type Selection, select View Site Edition (Network Distributed), and click Continue.

3. Select the InstantFizz application and click Open.

43 of 132
4. Once the application is opened, go to InstantFizz → HMI_Area → InstantFizz_HMI → Graphics →
Displays.

5. Expand the Displays section. Let’s make the changes that we were assigned by the engineering and
manufacturing department.

 Delete Object: Open the Lg_Packaging display and delete the FT AssetCentre & TrendPro
Integration button from the display. From your keyboard, press Ctrl + F4 to close the display, and click
Yes to save the changes.

 Delete Display: Select the Lg_Packaging_TrendPro display, right click, and click Delete to delete the
display from the application.

6. We are done making the new changes! Let’s minimize FactoryTalk View Studio.

44 of 132
Execute a Schedule
In this section of the lab, we will explore the FactoryTalk View Site Edition compare options. We will also execute a
Disaster Recovery schedule. The comparison results will then be viewed.
1. Let’s go back to the AssetCentre Client.
2. From the Schedules plug-in, select the ViewSE_App asset, and under the ViewSE_App Properties, go to
Compare Options and click the browse button.

3. Notice all the compare options available. All options are checked by default.

45 of 132
4. Let’s uncheck all options from the root – CompareOptions, and let’s check Displays under Graphics. Click OK.

5. Click Save to save the new task configuration.

46 of 132
6. Ensure that the ViewSE_App is the only asset selected in the schedule.

7. Click the Run Now button to launch the schedule.

8. Upon completion, the task will show that differences were found.

9. Open the Logs plug-in and select Event Log .

10. Find the most recent Disaster Recovery task completion (noted by the yellow triangle Warning severity) and
double-click the paper clip icon.

47 of 132
11. Click View to open the compare report.

12. Notice that the report provides a binary comparison. We can see that the HMI server Compare Project has been
modified and it’s different from the Base Project. A display was changed, and a display was deleted, which
correlates to the changes we made in the previous section.

13. Close the compare report, then Close the Attachment pop up.

48 of 132
Recovering Application Changes
In this section of the lab, we will recover displays from an archived application by leveraging the Application Export
functionality.
We have been informed that the changes we made to the ViewSE_App were not approved and that the application
must be recovered to the previous state.
1. From the AssetCentre Client, open the Archive plug-in.
2. Ensure the ViewSE_App_Backup.apb is selected from the Asset View.
3. From within the Archive, select Version 1, right click, and select Show in Application Export Window.

4. Select OK in the Get operation window.

49 of 132
5. The Application Export Window will be launched. Note that the InstantFizz HMI server is listed. Click the
browse button under Server Name.

The Application Export Window extracts the HMI server project from the FactoryTalk View Site
Edition application file (APB). This functionality allows the user to export specific files out of the
HMI server project without having to check-out the application from the archive. If the user checks
out the application, the FactoryTalk View SE Application Manager must be used in order to extract
specific files.

6. A new window will be launched with the InstantFizz_HMI project files. By default, they are all unchecked.

50 of 132
7. Let’s select the displays that we need to recover. Go to Gfx and click on the chevron to expand the list.
Scroll down, and check the lg_packaging.gfx and lg_packaging_trendpro.gfx displays. Click OK.
Note that you can “hover over” the items and you will see the last time the display was modified.

8. Select the browse button to select a target folder to export the files. Select the Desktop
C:\Users\Labuser\Desktop and click OK. Click Export.

9. Notice the progress export bar.

51 of 132
10. You will receive a pop-up window indicating that the operation succeeded. Click OK.
Ensure the pop-up window is not behind another application window.

11. Go to the Desktop and locate the InstantFizz_HMI folder. Open the folder and confirm that the displays were
exported.

12. Let’s go back to the FactoryTalk View Studio application.

13. Right click under Displays and select Add Component Into Application.

14. Browse to the Desktop and locate the InstantFizz_HMI folder. Select both displays and click Open.

15. Click Yes to All to continue with the import.

52 of 132
16. Scroll down, and notice that the displays have been recovered.

17. You can close the FactoryTalk View Studio application.

53 of 132
BONUS! FactoryTalk AssetCentre and FactoryTalk View SE TrendPro Integration
In this section you will launch the InstantFizz SE Client to view the FactoryTalk AssetCentre and FactoryTalk View
SE TrendPro Integration.
As of version 11.00 of FactoryTalk View SE and version 9.00 of FactoryTalk AssetCentre, TrendPro control object
can be configured to display FactoryTalk AssetCentre Audit and Event Logs from within the FactoryTalk View SE
client. The benefit of this integration is to bring important production information into a common, easy to use
environment.

1. From the Desktop, double-click the InstantFizz_SEClient icon.

2. From the navigation menu, navigate to the Packaging area.

3. Notice the FT AssetCentre & TrendPro Integration button with the NEW symbol.

4. Click the button.

5. The TrendPro screen will be launched.

6. To the left side of the trend, notice the new AssetCentre connector.

TrendPro can automatically retrieve AssetCentre Log information, and overlay operator actions and
AssetCentre system events as a trend, along with alarms from FT Alarms & Events

54 of 132
7. Select the AssetCentre connector, click on Audit , and “drag and drop” the item in the trend.

8. Notice the Enable/Disable Fault buttons to the right of the screen. For demonstration purposes, let’s simulate an
action. Click on the Enable Fault button.

9. TrendPro has captured the enable fault action and it has also retrieved the audit from the AssetCentre database.

55 of 132
10. Let’s disable the simulated fault. Click on the Disable Fault button.

11. TrendPro has captured the disable fault action and it has also retrieved the audit from the AssetCentre database.

12. Now you can correlate production information with AssetCentre audit and event logs. Create a comprehensive
view that adds context to changing set point data, alarms that were triggered, and what operator actions were
taken.

13. Let’s close the FactoryTalk View SE Client. From the navigation menu, select MORE and then SHUTDOWN.
Select YES / EXIT to close the Client.

For more information on FactoryTalk View Site Edition TrendPro, please refer to Rockwell Automation
Knowledgebase.

This completes the Disaster Recovery for FactoryTalk View Site Edition portion of the lab!

56 of 132
Section 04: Managing AssetCentre Database Size (25-30 minutes)

Through the course of normal operation, the FactoryTalk AssetCentre system’s database will grow in size. As the
database grows very large, the performance of the system can suffer (for example, longer client loading times). To
assist in keeping the database size reasonable, a variety of tools are offered.

Database Limitations Options: Used as a real time monitor of database size. Configurable options include
maximum diagnostics log sizes, maximum number of versions per archive asset, and maximum overall database
size. Alerts will be displayed in the AssetCentre client, and can also be configured as emails.

Archive Cleanup Wizard: Used to remove unnecessary versions of archived files from the database, thereby
clearing space. Removed versions are deleted from the database, but the version number and associated notes are
retained in archive for the purposes of record keeping. The Archive Clean-up can be run manually from the
FactoryTalk AssetCentre client, or it can be scripted to run automatically (e.g., as a Windows Task).

Log Cleanup Wizard: Used to remove unnecessary records from the Audit, Event, and Diagnostics and Health logs.
Removed logs can be exported for future reference, or simply deleted. The Log Clean-up Wizard can run manually
from the FactoryTalk AssetCentre client, or it can be scripted to run automatically (e.g., as a Windows Task).

Configuring Database Limitations

In this section of the lab, you will learn how to configure database alerts for the AssetCentre system.

1. Launch the FactoryTalk AssetCentre Client, if it’s not already open.

2. Open Tools  Options

57 of 132
3. Select Database Limitations. Notice that the checkbox is checked, meaning Database Limitations are already
enabled.

4. It is also possible to see that Database Limitations are enabled by viewing the database status at the bottom of
the AssetCentre Client

5. Modify the Maximum number of versions per archive asset to 100.

6. Scroll to the bottom and notice the OK button is not enabled. You must first push SCAN to proceed.

The scan will confirm that all settings are within the current database size. If not, they cannot be saved.

58 of 132
7. Notice that the scan has failed. One of the archived assets, Batch_CLX.acd, has more than 100 versions.

Note: The link to the file also appears with too many versions. Because this is a shortcut,
modifying the base file is all that is required.

8. Click Close, then Cancel.

Our updated Database Limitations settings cannot be saved until the current database is within the desired limits.
With that in mind, we’ll need to clean up some of the versions of the Batch_CLX.acd file.

59 of 132
Create Archive Cleanup Configuration File
In this section of the lab, you’ll learn how to use the Archive Cleanup Wizard, and how to automate a cleanup
process from the command line. To create a configuration file for use with the manual or scripted utility, the Archive
Clean-up Wizard must be run from the FactoryTalk AssetCentre client.

1. Open Tools  Archive Cleanup Wizard

2. Click Next

3. The wizard will provide general information on the archive. Click Next.

4. The wizard will now prompt for the files that will be cleaned up as part of this operation.

60 of 132
5. Browse to AssetCentre  Files  Studio 5000  Projects  Batch_CLX.ACD and click Add to list

6. Click Next

7. In the Keep field, enter the number 98, and select today’s date in the right-most date field.
This will configure the clean-up utility to remove all but the 98 most recent versions.
Click Next.

Note: Selecting the Advanced option allows the user to specify settings for each file in the
configuration. The user may select from date range, as seen here, or version range (e.g., versions
2-20.)

61 of 132
8. Retain the defaults and click Next.

As of version 8.0, it is possible to clean up the archive comments as well as the versions. This
ensures that the comments do not take up extra database space.

9. Click Save Configuration

62 of 132
10. Navigate to C:\Lab Files\Archive Cleanup and save the configuration as Cleanup.

11. Click Save.

12. Click Cancel.

It is possible to manually run the utility here using the Start button. In the next section, however, the configuration
file will be used as part of the scripted utility, so do not run the utility at this point.

63 of 132
13. Navigate to C:\Lab Files\Archive Cleanup

14. Right-click on the newly created Cleanup.xml and select Edit.

15. Locate the <END DATE> section. Remove today’s date and replace it with now.

Note: Using now allows the configuration file to be used multiple times without being constrained
to a particular date range. Now can also be used in conjunction with -# to indicate a certain
number of days ago. For instance, now -10 indicates 10 days ago. An example of this could be
used to say keep 0 versions that are more than 10 days old.

16. Save the changes and exit out of Notepad.

64 of 132
Execute Archive Cleanup Utility from Command Line
This section will show how to run the archive cleanup utility from a command line, which allows for the scheduling of
cleanup operations. When run outside of the FactoryTalk AssetCentre client, the Archive Clean-up Utility makes use
of stored credentials. This section will show how to configure those credentials.

1. Right click the Configure_Security.bat and select Run as Administration.

Note: The Configure_Security batch file has been created for use with this lab to simplify the
typing needs. To launch the security configuration screen, the archive clean-up utility’s executable
file (located in the AssetCentre Client directory) must be launched with the /c command.

2. The security configuration screen will appear. Enter Username of ‘labuser’ and a Password of ‘rockwell’
Click the Test button to ensure that the credentials are entered correctly.

3. Click OK to continue, which will close the dialog and complete the security configuration.

65 of 132
4. Right click the Launch_Utility.bat and select Run as Administration.

5. A command prompt window will be displayed as the utility completes (approximately 30 seconds.)

Note: The Launch_Utility batch file has been created for use with this lab to simplify the typing
needs. To launch the utility normally, the archive clean-up utility’s executable file (located in the
AssetCentre Server\bin directory) must be launched with a reference to the configuration file.

For example: RA.FTAC.ArchiveCleanUp.exe "C:\Lab Files\Archive Clean-up\Cleanup.xml"

This method can also be used to schedule archive clean-up using Custom Device Plug-in
functionality.

6. When the command prompt window disappears, the utility has completed.

66 of 132
View Archive Clean-up Utility Results

1. In the AssetCentre Client, open the Logs tab and select Event Log

2. Look in the Message column to see Archive cleanup operation completed.

3. Double-click the paper clip icon in the top entry and click View

4. The log file will indicate all changes made. Notice that the first version of the file was kept, but all other versions
were removed. The archive clean-up utility can remove any version except the first and last version of a file.

67 of 132
5. Scroll down and notice that after version 49, nothing was deleted. Because there were 148 versions, and the first
version cannot be deleted, this means a total of 100 versions were not deleted.

6. Close the log file and attachment dialog.

7. Browse in the Asset Tree to AssetCentre  Files  Studio 5000  Projects  Batch_CLX.ACD and open
the Archive tab. Notice the total version count is down to 100, and version 49 is grayed out. Version 49 has
been removed from the database, but its history is still included in the versions view.

Note: While the versions have been removed from the database, thereby freeing up hard drive
space, the version information in the FactoryTalk AssetCentre archive remain for future reference.

Now that the version count is down to 100, the database limitations can be saved. Before doing so, let’s also clean
up the diagnostics logs.

68 of 132
Diagnostic Log Cleanup Wizard
Like the Archive Cleanup Wizard, the log cleanup wizard can also be configured to run on a scheduled basis. Before
configuring the command line, this section of the lab will walk through the manual steps.

1. Click Tools  Log Cleanup Wizard.

2. Click Next to the Welcome Screen.

3. Select Audit Log as the Log we want to clean up or process, click Next.

Note: Audit, Events and Diagnostics Log are treated separately. If you wanted to clean out the
Event or Diagnostics, the Clean-up wizard would need to be run once per category.

69 of 132
4. For the Log Date Criteria, Enter Yesterday’s date. (It is not possible to enter today or a future date.) You can
use the drop down to do this.

5. With the Export data to file selected, change the File Name to myAudits.sdf and change the File Path to the
Desktop.

6. Click Next to advance to the Confirmation Screen.

7. Use the Set Log File button to create the log file on the Desktop, then click Start.

8. The process will take around 60 seconds to complete.

9. Once the process is complete a Results screen is displayed, click Next.

70 of 132
10. The Log Cleanup Wizard shows the before and after effects of processing, Click Finish to exit.

Note: Some rows may remain; this is primarily due to the today’s Audit messages remaining in the
database. The numbers shown above may not exactly match what you’re seeing.

71 of 132
Configuring Log Cleanup from Command Line
It is possible to configure the Log Cleanup utility to be run from a command line, thus allowing log cleanups to be
scheduled using Windows Scheduled Tasks. The following section demonstrates how to configure the Log Cleanup
utility for use through a command line.

1. Navigate to C:\Lab Files\Log Cleanup

2. Right click the Configure_Cleanup.bat file and select Run as Administrator.

Note: The cleanup utility is located in the AssetCentre Client’s installation folder.

72 of 132
3. Refer to the picture below for configuration options:

Note:
 It is possible to clean all log types as part of the same operation. Each type of Log will
generate a different backup file, if applicable; they are not combined into one.
 The default value of 1 day will only keep the logs of the date on which the utility is run.
 Deleting the log data without saving will permanently delete the records with no ability for
recovery.
 There is no ability to name the output. It is time and date stamped upon utility execution.

73 of 132
Execute Log Cleanup from Command Line
Once configured, the Log Cleanup Wizard can be run from a command line by launching its executable. While this
could be configured as Custom Device Plug-in functionality, this lab will manually run the cleanup.

1. Right click the Run_Cleanup.bat file and select Run as Administrator.

2. Note the status in the command window, which will take about 60 seconds to complete.
The command includes a pause at the end of the file so the results can be viewed. This pause would not be
required as part of a Windows scheduled task or Custom Device asset.

3. Close the command prompt window.

4. Navigate to the desktop and double-click the Event Log Cleanup text file (the time/date stamp will vary.)

The utility will produce a text file for each type of log cleaned (e.g., one for events, one for audits,)
as well as an SDF backup for each if specified in the configuration. Each file is identified by the
type of log cleaned, as well as the date and time stamp when the utility was executed.

74 of 132
5. The text file shows the results of the cleanup operation. Close the text file.

6. Return to the AssetCentre Client and open the Event Log.

7. Clear any existing filters.

8. Note that the log cleanup is posted to the event log, along with the same text file as an attachment.

75 of 132
View Purged Log data
1. To View the records that were just created from the FactoryTalk AssetCentre database start the Log Viewer by
typing Log Viewer under the Windows Search option .

2. Select the FactoryTalk AssetCentre Exported Log Viewer result.

3. To open the myAudits.sdf file, click Open Log and browse to the desktop and select “myAudits.sdf”, then click
Open.

4. The contents that have been removed from the AssetCentre logs can now be viewed here.

5. Close the Log Viewer when complete.

76 of 132
Configuring Database Limitations (again)
In this section of the lab, you will return to the Database Limitations section to save an updated configuration.

1. Launch the FactoryTalk AssetCentre Client, if it’s not already open.

2. Open Tools  Options

3. Select Database Limitations.

4. Modify the Maximum number of versions per archive asset to 100.

5. Scroll to the bottom and push SCAN to proceed.

77 of 132
6. All areas now pass the scan and can be saved! Click Close.

7. The OK button is now enabled. Click it to proceed

8. All archived assets now have a global limitation of 100 versions, but we can overwrite this limit at a local level if
more granularity is needed. Select AssetCentre  Files  Studio 5000  Projects  Washer_CLX.ACD
and open the Archive tab.

9. This file changes much less frequently than Batch_CLX, so we can reduce the total number of versions allowed.
Check the Maximum number of versions box, enter 25, and click Save.

The Batch_CLX file can now have a maximum of 25 versions, while the other archived files can go up to 100.

The system is now configured to automatically limit the total number of archive versions, and you have configurations
available to automate the cleanup of the archive and diagnostic logs!

78 of 132
Section 05: Securing FactoryTalk AssetCentre (15-20 minutes)

In this section of the lab you will secure FactoryTalk AssetCentre assets and features. You will restrict Design Mode
access to appropriate users, and configure the Asset Tree’s visibility such that users from different areas cannot
interact with an area to which they do not belong.

Launching FactoryTalk AssetCentre

1. Open FactoryTalk AssetCentre Client from the Start menu, if it’s not already open.

Notice the logged in user on the bottom status bar:

79 of 132
Creating new Users and Groups
To secure our FactoryTalk AssetCentre asset view and features, we will first need to create new users and groups for
our Packaging and Process Areas. Users and groups are administered in the FactoryTalk Administration Console.
1. Open FactoryTalk Administration Console from the shortcut on the desktop.

2. Select the Network FactoryTalk Directory and click OK.

After a few seconds you will see the FactoryTalk Administration Console

80 of 132
3. Expand the Users and Groups, then expand Users then expand User Groups

4. With the User Groups folder selected, right click and select New  User Group

81 of 132
5. Enter Process Area for the Name, then click Add

6. Let’s create a new user to add to this group. Select Show users only for the Filter Users, then click Create
New and select FactoryTalk User.

7. Enter ftuser1 for the User Name and rockwell for the password.

82 of 132
8. Click OK to continue.

9. Select ftuser1 in the list and then click OK

83 of 132
10. The ftuser1 has been added to the Process Area group. Click OK to the new User Group dialog with our
assigned Users.

Next, we are going to create a new User Group to represent the Packaging Area, and a new user to assign to it.

11. With the User Groups folder selected, right click and select New  User Group.

12. Enter Packaging Area for the Name, then click Add.

84 of 132
13. Let’s create another new user. Select Show users only for the Filter Users and then click Create New and
select FactoryTalk User.

14. Enter ftuser2 for the User Name, and rockwell for the password, and click OK.

15. Select ftuser2 in the list and then click OK.

16. ftuser2 has been added to the Packaging Area group.

Click OK to the new User Group dialog with our assigned Users.
Our FactoryTalk Administration Console explorer should now look like this:

85 of 132
Securing AssetCentre functions (Design Mode)
Now that we have our Process Area and Packaging Area Users Group and Users created, we are going to restrict
these groups from entering into Design Mode within AssetCentre.

1. Browse to the Policies  Product Policies  FactoryTalk AssetCentre folder

2. Double-click on the Feature Security item

3. Navigate to the Switch to Design Mode polices and click the Configure Security button.

86 of 132
4. Click the Add button

5. Select Packaging Area and click OK

6. Again, Click the Add button

7. Select Process Area and click OK

8. Restrict their access to enter Design mode by clicking the Deny checkbox for both, then click OK..

9. Click OK to close the Feature Security Properties dialog.

10. Close the FactoryTalk Administration Console.

87 of 132
Securing the FactoryTalk AssetCentre Asset Tree
You will now configure security to prevent the two groups (Process and Packaging Area’s) from viewing each other’s
assets or areas.

1. In the FactoryTalk AssetCentre client, enter Design mode.

2. Navigate to the Packaging Area and click the Configure Security for the Selected Asset button..

The following window displays the current access privileges to this asset:

88 of 132
3. Click the Add button

4. We want to block the Process Area group from interacting with the Packaging Area assets, so select the
Process Area group and click OK.

5. Expand out the Common Permissions, navigate to List Children.

6. Check Deny for the List Children permission, then click OK.

Note: This will prevent any user associated with the Process Area user group from viewing the
Packaging Area contents.

89 of 132
7. Click Yes to the Security Settings dialog.
8. Next, navigate to the Process Area so we can block it from the Packaging Area users.

9. Next, click the “Configure Security for the Selected Asset” button.

10. Click the Add button to add the Packaging Area group, then deny its List Children permission.

11. Click OK to confirm the settings, and Yes on the security dialog.

12. Exit design mode by clicking the Design button.

90 of 132
Exercise Security Configuration
In this section of the lab we are going to confirm the new security configuration!

1. Within the AssetCentre client, click File and then Log Off.

Notice, with no user log in the FactoryTalk AssetCentre client is blank.

2. To Log back in, click File and then Log On

3. Log in as ftuser1 with the password of rockwell.

91 of 132
4. The FactoryTalk AssetCentre client opens.
Remember: ftuser1 is a member of the Process Area, so this user does not have any access to the Packaging
Area. Additionally, they are barred from access to Design Mode.

5. Let’s Log Off as ftuser1 and Log In as ftuser2 (remember, the password is still rockwell).

6. As a member of the Packaging Area, ftuser2 cannot interact with the Process Area or enter Design Mode.

7. Finally, Log Off and Log On as labuser with the password rockwell.

This completes the Securing FactoryTalk AssetCentre portion of the lab!

92 of 132
Section 06: Disaster Recovery for ControlLogix (15-20 minutes)

ControlLogix Disaster Recovery allows for the automated backup and comparison of program files running in
ControlLogix controllers. Once a ControlLogix device is configured as an asset in the FactoryTalk AssetCentre asset
tree, it can be added to a Disaster Recovery schedule. The results of the Disaster Recovery schedule are added to
the FactoryTalk AssetCentre Event Log, and can also be configured to be emailed. This appendix will walk through
how to add and configure a new ControlLogix asset, configure it for Disaster Recovery, then execute a Disaster
Recovery schedule against it.

Retrieve ACD File

Before creating the new asset, this section will walk through acquiring the ACD file from the FactoryTalk AssetCentre
archive. In a typical situation, the ACD file would not already exist in the AssetCentre archive, but this lab is using an
existing file for simplicity.

1. Open the FactoryTalk AssetCentre client, if it’s not already open.

2. Navigate to AssetCentre  Files  Studio 5000  Projects.

93 of 132
3. Select Filler_CLX.ACD and open the Archive tab.

4. Select Version 22 then click the Get Version button.

94 of 132
5. Select Get writeable copy and Override working folders with path. Use the Browse button to select the
desktop.

6. Click OK.

7. On the desktop, double-click the ACD file to open it in Logix Designer.

8. Double-click Controller Tags

95 of 132
9. Change SP_Actual to 24.

10. Click Save and exit Logix Designer.

Configure Logix 5000 Asset

In this section of the lab, a new asset will be configured to point to the same ControlLogix as the existing Filler_CLX
asset. This will not cause any problems in FactoryTalk AssetCentre, but creating duplicate assets outside of test
purposes is not worthwhile.

1. From the FactoryTalk AssetCentre client, click the Design button to enter design mode.

2. Browse to AssetCentre  Plant Layout  Packaging Area.

3. Click the Add button.

96 of 132
4. Select Generic Container and click OK.

5. Name it Filler Line 2 and click OK.

97 of 132
6. The new container will be added to the tree. Select it and click the Add button again.

7. Select Logix5000 Controller and click OK.

8. Name it Filler2_CLX and then click the Addressing Info browse button

98 of 132
9. In the RSLinx Classic RSWho window to and select AB_VBP-1 → 02, RSLogix 5000 Emulator, Filler_CLX.

Note: If a ControlLogix device can be browsed to using RSLinx Classic, it can be added to
FactoryTalk AssetCentre. RSLinx Classic is the communication software used to connect to Logix
5000 assets.

10. Click Select.

11. Notice that a number of read-only properties have been filled in automatically. Now click the Configuration
Data browse button.

99 of 132
12. Click the Add button.

13. Browse to the Desktop and select the Filler_CLX.ACD file. Click Open.

100 of 132
14. Select the Filler_CLX.ACD file and click OK. This will add the file to the archive and associate it with the new
ControlLogix asset.

15. The ControlLogix’s asset configuration is complete. Click OK to finalize the configuration.

16. Expand the new container and asset in the asset tree. Notice that the file has been added as a child node of the
ControlLogix asset.

Note: Configuration Data files like Filler_CLX.ACD do not have to be added to the asset tree below
their corresponding asset. They can be added anywhere in the asset tree.
ACD files can be version controlled by the FactoryTalk AssetCentre archive and are associated
with ControlLogix assets to allow for comparison operations against production versions.

17. Click the Design button again to disable Design mode.

101 of 132
Configure ControlLogix Disaster Recovery
Once a ControlLogix asset has been added to the asset tree, it can be configured for use in a Disaster Recovery
schedule. This section of the lab will explore the Disaster Recovery configuration, including tag filtering.

1. To start the Scheduling plug-in, click the Schedules button. The Scheduling plug-in will open in
the workspace pane.

2. Select the Weekly schedule.

3. In the lower pane, select View by Asset Type to show all assets by device.

Notice that the new asset has already been added to the Weekly schedule because the schedule was configured
to include all assets in the AssetCentre asset tree. It will dynamically update with any additions or removals.

4. Uncheck Asset Types, and ensure Filler2_CLX is checked.

102 of 132
5. Note the Disaster Recovery Task properties:

Master File Path Name: Derived from the Configuration Data property, this is the file against
which comparisons will be made.
Promote New Upload to Master: Determines whether a new archive version will be created if
differences are detected.
Report Incremental Differences: Allows the user to split the file stream between a production
version for comparison and a development version.
Always Run Events: If set to False, FactoryTalk AssetCentre will use the ControlLogix Change
Log to determine if an upload and comparison need to be run prior to performing any actions.
Compare Options: Set which parts of a project get compared following an upload.
Tag Filter: Allows for the selection of specific tags for comparison (versus all tags or all constant
tags.)

6. Click the Compare Options browse button.

103 of 132
7. Select Tag Filter then click OK.

8. Now that the Tag Filter is enabled, select and open it using the browse button.

Note: It may take a few moments for the Tag Filter dialog to populate, as the ACD file is currently
being opened and queried for all available tags.

9. The Tag Filter dialog will open, looking similar to this:

104 of 132
10. Expand Controller Tags and select SP_Actual.

Note: When the comparison between the production program and archive program is made, it will
now alert on any differences in the SP_Actual tag value.

11. Click Next.

12. Click Finish.

13. Save the changes to the scheduled task.

105 of 132
Execute ControlLogix Disaster Recovery Task
In this section of the lab, a Disaster Recovery schedule including a ControlLogix task will be executed. The
comparison results will then be viewed.

1. Ensure that Filler2_CLX is the only asset selected in the schedule.

2. Click the Run Now button to launch the schedule

3. The Task will show a Running state until completed. This will take approximately 1 minute.

106 of 132
4. Upon completion, the task will show that differences were found.

5. Open the Logs tab and select Event Log.

6. Find the most recent Disaster Recovery task completion (noted by the yellow triangle Warning severity) and
double-click the paper clip icon.

7. Click View to open the compare report.

8. The compare report will show one tag difference, configured from the tag filter, and some program differences.
This is expected because the latest version was not extracted from the archive, and a manual value change was
made as part of the lab.

107 of 132
9. Scroll down to the second page to see the tag value comparison.

Tag Value comparison options range from individual tag selections, as shown here, to all Constant
Tags, to all tags. Most programs will not use the option to compare all tags because most
programs have changing tags as part of normal operation.

10. Scroll to page 4 to see tag differences.

This comparison shows that there are two tags existing in the controller than have not been
created in the configured ACD file. If the lab wasn’t using a known older version of the file, this
could have been through an online change, which would be shown in the audit logs.

11. Scroll to page 5 to see rung changes.

The Logix 5000 Compare Utility shows a graphic representation of any rung differences. In this
comparison, Rung 0 is different in the controller, and Rung 1 has been added.

12. Close the compare report, then Close the Attachment pop up.

This completes the ControlLogix Disaster Recovery portion of the lab!

108 of 132
Section 07: Using Custom Device Disaster Recovery with 3rd-Party Scripting Tool (20-25 minutes)

In this section of the lab, you will learn how to configure a Custom Device Plug-in asset and corresponding Disaster
Recovery Schedule to backup a ControlLogix controller using AutoIt scripting language (open source). AutoIt is a
freeware scripting language available for download (https://www.autoitscript.com/site/).

Note: This section utilizes the FactoryTalk AssetCentre Custom Device Plug-in capability add-on,
AutoIt scripting language, and Studio 5000 Logix Designer. This sample solution is intended to
provide a guideline for anyone that needs to develop scripts to perform Disaster Recovery
operations with third-party devices.

For more information on the Custom Device Disaster Recovery with Third-Party Scripting Language Tool solution,
please refer to Answer ID 1085184 on the Rockwell Automation Knowledgebase. The AID contains a how-to-guide
document with requirements, script definition, and so on, plus it includes the AutoIt backup and compare scripts, and
executables.

In summary, this working sample solution leverages the Custom Device Plug-in capability by using an open source
scripting tool (keystroke simulation) to perform a Disaster Recovery Backup task of an asset (third-party device). To
provide a familiar asset example, the asset being used is a ControlLogix controller.

Custom Device Configuration

The first step in configuring a Custom Device Plug-in asset is to create the Custom Device Configuration, which is
global definition.

1. Open the FactoryTalk AssetCentre Client from the Start menu.

2. From the AssetCentre Client, open Tools → Options.

109 of 132
3. Select Custom Devices.

4. The Custom Device profiles currently configured will be displayed.

Custom Device
Profiles Properties
Custom Device
Profiles

5. Click the Add New button.

110 of 132
6. Enter Logix5K_AutoIt_Backup as the Description. Next, let’s create the Backup Configuration.

Backup Configuration: Consists of a command, argument (ARG), delay, backup location for
backup files, and success return code. The command defined here is the main action the
FactoryTalk AssetCentre Agent will perform during the disaster recovery schedule backup
operation.

7. Click the Browse button for the Backup Configuration Command.

Command: The command line contains the file the FactoryTalk AssetCentre Agent will execute.
This could be an executable (*.exe), batch (*.bat), visual basic script (*.vbs), or Microsoft
PowerShell™ script (*.ps1.)

111 of 132
8. In the Command Editor, click the Program browse button.

9. Select C:\AutoIt\Logix5K_Backup_Update.exe, click Open.

112 of 132
10. The Agent will need to pass two arguments to the AutoIt executable when it is executed. First, let’s add a device
argument by selecting Device Argument <ARD>, and clicking the right arrow . Then follow the same
process to move <SPACE> and Global Argument <ARG> to the right window.

Note that the up & down buttons manage the order of the configured arguments, and the left arrow button
removes the selected argument from the list. The Device Argument <ARD> and the Global Argument <ARG>
order of execution will depend on the tool being used.

Device Argument <ARD>: This is an argument defined in the Custom Device asset properties for
the Backup, Compare, or Post Backup actions. The ARD will be appended to the command
executed by a FactoryTalk AssetCentre. An ARD allows for individual asset customization,
whereas the Custom Device Configuration and ARG properties are applied to all Custom Device
Assets making reference to them.
<SPACE>: This allows for the insertion of a space between the global argument and device
argument. There will always be a space between the command itself and the first argument, but by
default, there’s no space in between the arguments unless manually configured.
Global Argument <ARG>: This is an argument defined in the Custom Device Configuration for
the Backup, Compare, or Post Backup actions. The ARG will be appended to the command
executed by a FactoryTalk AssetCentre. An ARG is a global property inherited by any Custom
Device asset making reference to its Custom Device Configuration.

113 of 132
11. When configured, the Command Editor – Backup window should look like the following.

12. Click OK.

13. Notice that the Backup Configuration Command property now includes an ARD and ARG placeholders. To
define the Argument <ARG>, select the button to add the required mnemonic. This argument will apply to all
assets configured with the Logix5K_AutoIt_BackupCompare Custom Device.

114 of 132
14. Select %BackupFolderPath% and click OK.

The %BackupFolderPath% mnemonic will be used by the Agent to save the file and check-in into
the archive. In this example, the AutoIt backup executable will use the first parameter <ARD> to
open the project file defined at the device level followed by the second parameter <ARG> to save
and “check-in” the file into the archive. The <ARD> parameter will be defined under the Custom
Device asset configuration.

15. Click OK.

16. Next to the Delay (seconds) property, increase the value to 1800 seconds to ensure the command completes
on time.

Delay (seconds): Is the number of seconds that the Agent process will wait for the command to
complete. If the command does not complete prior to the delay expiring, the Agent process will
terminate the command and issue a timeout error. Setting the field to 0 (default) tells the agent
process to wait infinitely for the command to complete.

115 of 132
17. The Backup Location and Success Return Code will be left at default.

18. The Backup Configuration properties should look like the following.

Backup Location: Depending on the configuration, this property corresponds to the path where
the Agent will retrieve the backup files to be checked into the Archive when manually defining the
<ARG>; or where the Agent will store a copy of the backup files when using a mnemonic as the
<ARG> as part of a Disaster Recovery schedule. The backup files will be stored as a binder asset.

Important: This path must be relative to the agent computer, not the client computer.

Success Return Code: Corresponds to one or multiple integers that are defined as the success
exit codes in the application script. The default value is 0.

116 of 132
19. The new Custom Device configuration is complete. Click OK to continue.

20. Now we are ready to create a new Custom Device asset!

117 of 132
Create Custom Device Asset
With a Custom Device Configuration created, an asset can be created to reference it. This asset can be used as part
of a Disaster Recovery backup operation.

1. Click the Design button to enter design mode.

2. Navigate to AssetCentre → Plant Layout → Packaging Area → Filler.

3. In the Device Items Catalog, select Custom Device and Click the Add Custom Device to Filler button.

118 of 132
4. Enter the name myCustomDevice_Logix.

5. Select the Configuration Data property and click the browse button to select the binder for use with the
asset. For this example, we are using a binder containing the controller project file (Filler_CLX.ACD). Assigning
a Backup Data binder is not necessary, as one will be created upon the first execution of the Disaster Recovery
Task.

6. Click Add.

7. Name the binder myCustomDevice_Logix Project.

8. Use the Source Folder Browse button to navigate to C:\AutoIt\LogixProject and click OK. The Add Binder
display should look like the following.

9. Click OK.

10. Click OK again on the Configuration Data Browse window.

119 of 132
11. Under the Backup property, select the Custom Configuration property, and click the browse button.

12. Select the Logix5K_AutoIt_Backup configuration that we just created. Notice that a preview of the
configuration is displayed in the right pane. Click OK.

120 of 132
13. Since the Logix controller project file is a device level property, the Arguments <ARD> property can now be
completed. Under the Backup property, click the browse button to enter the Arguments <ARD> (device
argument).

14. Within the Argument Editor – Backup, enter the path and name of the controller project file. In this example,
we are using Filler_CLX.ACD file as the controller project file.
C:\AutoIt\LogixProject\Filler_CLX.ACD
Filler_CLX.ACD refers to the device file being used
15. Press the Check button when complete. Notice that the command can now be previewed in the lower pane, and
that it matches the expected format for the AutoIt executable.

16. Click OK.

17. The Backup Location is optional for this example and will not be defined.

18. The Backup properties configuration should look like the following.

19. The asset configuration is complete! Click OK to continue.

121 of 132
20. Click the Design button again to disable design mode.

21. With the new Custom Device asset configured, let’s create a Disaster Recovery Schedule.

122 of 132
Execute Custom Device Disaster Recovery Task
Once a Custom Device Asset has been configured, it can be used as part of a Disaster Recovery schedule.
Continue with this section to learn how.

1. Click the button to start the Schedules plug-in.

2. With the newly created asset selected, click the button to create a new schedule for backup operation
tasks.

3. From the New Schedule Wizard, select the Operation for Disaster Recovery – Backup and enter
myCustomDevices next to Name.

4. Select Next.

5. Select Next for the Timing Properties step.

123 of 132
6. And select Finished to complete the new Backup Schedule.

7. Important! As stated previously, the AutoIt scripting language utilizes keystroke simulation, which requires the
AgentController service to run as an Application as it requires application interaction. This must be configured in
the Agent computer responsible for executing any task(s) using AutoIt scripting language.

In general, it is recommended to have a dedicated Agent computer to execute Custom Devices for
third-party assets using the AutoIt scripting language (or other keystroke simulation/mouse click
utilities) as it is required to run the AgentController service as an application. Consider using Agent
Groups to ensure that no other agents attempt the custom device operation and that the
responsible Agent will not be used for other tasks.
For information on building a system using agent groups see the FactoryTalk AssetCentre Design
Considerations in AID 57483.

124 of 132
8. From the Start menu, select the Agent Controller Launch Control Panel.

10. Ensure that the AgentController service is running as an Application.

11. Select to close the control panel.

125 of 132
9. With the asset’s scheduled task configured, click the button to run the schedule and immediately
minimize the AssetCentre Client and any other applications including the RSLogix Emulate 5000 Chassis.

PLEASE READ! Do not perform other activities in the Agent computer while tasks are being
performed when the AgentController service is running as an application. The AutoIt scripting
language has been configured to use keystroke simulation, which can be interrupted if other
activities are taking place.

The Desktop should look like this before the backup operation starts.

10. Relax and enjoy while you watch the backup operation of the Custom Device asset you just created. The
schedule will download the configuration binder from the archive, then execute the configured commands. The
backup operation task should take less than 2 minutes to complete.

11. You’ll notice that the operation is complete when Studio 5000 Logix Designer closes.

12. Once the operation is complete, go back to the AssetCentre Client that was previously minimized.

13. Notice that the backup schedule was completed successfully. When the task completes, a new Backup Data
binder will be added.

126 of 132
14. From the toolbar, click the button to open the Archive plug-in, and select the newly created Backup
binder.

This completes the Custom Device Disaster Recovery with Third-Party Scripting Language Tool portion of the lab!

127 of 132
Section 08: Stratix Switch Archive to Archive Comparison (10-15 minutes)

Archive to Archive Compare refers to the ability for the FactoryTalk AssetCentre Client to compare different files or
versions of the same file from within the archive itself, without requiring a check-out. File comparison is not limited to
just the archive; a file from archive can also be compared to one on the desktop, or two files that are not part of the
FactoryTalk AssetCentre database can be compared to each other.
In this section of the lab, you will work with a new asset type called Stratix Switch. Using the Stratix Switch asset,
you can automatically back up and compare the switch data including the configuration file (config.txt), the VLAN file
(vlan.dat), and the DLR file (dlr.dat – when configured) via Telnet or Secure Shell (SSH). A Stratix Switch compare
operation type returns a detailed compare report of the config.text file and a checksum report of the vlan.dat and
dlr.dat files.
In this section, you will be comparing a two Stratix Switch archived versions to review detailed differences between
these two versions.

Launching FactoryTalk AssetCentre

In this section you will launch the FactoryTalk AssetCentre Client, if it’s not already open.

1. From the Start menu select AssetCentre Client. You can also double-click the FactoryTalk AssetCentre Client
icon on the desktop:

128 of 132
Archive to Archive Compare – Archive Only
In this portion of the lab you will walk through performing a comparison using only files that are checked into the
FactoryTalk AssetCentre Archive. In this example, we will be using the Stratix Switch asset archived files.

1. From the AssetCentre Client, navigate to AssetCentre → Plant Layout → Packaging Area → Filler →
Filler_Switch, select the Filler_Switch_backup, and open the Archive plug-in.
Notice that the Stratix Switch asset is backed up and archived leveraging the new Binder asset type.

2. Right-click on Version 1 and click Select Left File for RA Compare.

3. Right-click on Version 2 and click RA Compare to…

Note: The name of the file chosen first will be dynamically filled in here. If “Select Left File for RA
Compare” is chosen again, it will replace the first file chosen.

129 of 132
4. When the compare is complete, the RA Compare report will be displayed. Let’s see which files are different.
Notice that the RA Compare results indicate that both files, config and vlan are different.

Reading an RA Compare Folder Report

The RA Compare report shows the contents of the “left” folder (or first item selected as part of the
compare) as a list on the left side of the window, and the contents of the “right” folder (or second
item selected as part of the compare) as a list on the right side of the window.

in the middle column means the item is the same in both versions.

in the middle column means the item has differences. The filename shown in grey is the
older file, and the one shown in red is the more recent file.
Nothing in the middle column means the item has been added or deleted in one version.
Filenames shown in blue indicate its presence in one folder, and blank (no filename) to indicate its
absence in the other folder.

5. Let’s see what’s are the difference between these two versions. For demonstration purposes, the Disaster
Recovery detailed compare pdf report has been saved in C:\Lab Files folder location. Locate the
StratixSwitchCompareDeviceToBackup.pdf file. Open the pdf file.

Note: Older compare reports can be obtain from the Logs using the Quick Search functionality.

130 of 132
6. Once the pdf file is opened. Scroll down and notice the red text between the archive column and the production
column. A new user has been added to the switch as you can see from the production column. The new user
is named demo with read-only privileges.

7. Keep scrolling and notice the red text between the archive column and the production column. A VLAN has
been deleted from the switch as you can see from the archive column. VLAN 3 named myVLAN has been
deleted from the switch.

8. Any previous configuration can be obtained from the archived versions to recover the switch to its last know
operation state.
9. You can close the pdf.

For more information on the Stratix Switch asset configuration functionality, please refer to Rockwell Automation
Knowledgebase.

This completes the Stratix Switch Archive to Archive Comparison portion of the lab!

131 of 132
Notes

Copyright© 2019 Rockwell Automation, Inc. All rights reserved.

132 of 132