FactoryTalk AssetCentre® Design Considerations

FactoryTalk AssetCentre v9.00 (CPR9 SR11)

Best practices for designing and

implementing FactoryTalk AssetCentre
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

This page left intentionally blank.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 2 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Table of Contents
FactoryTalk AssetCentre® Design Considerations ............................................................................................ 1
Introduction ........................................................................................................................................................ 7
What’s New in this Document ....................................................................................................................... 7
Using this Document ...................................................................................................................................... 7
Document Naming Conventions/Abbreviations............................................................................................. 8
Prerequisite Reading ....................................................................................................................................... 8
Revision History ............................................................................................................................................. 9
What’s New in FactoryTalk AssetCentre v9.00 (CPR9 SR11)? ...................................................................... 10
Known Issues................................................................................................................................................ 10
What’s New in FactoryTalk AssetCentre v8.00 (CPR9 SR10)? ...................................................................... 11
Known Issues................................................................................................................................................ 11
Recommended Platform Requirements ............................................................................................................ 12
Windows Automatic Updates ....................................................................................................................... 12
Virtual Environments ................................................................................................................................... 12
Internet Information Services (IIS) .............................................................................................................. 12
Windows Environment ..................................................................................................................................... 13
Domain Best Practices .................................................................................................................................. 13
Network Configuration ..................................................................................................................................... 14
WAN/Wireless Communications ................................................................................................................. 14
Firewall Communications ............................................................................................................................ 14
Installation Best Practices................................................................................................................................. 14
FactoryTalk Services Platform ..................................................................................................................... 14
Component Architecture .............................................................................................................................. 15
Install Order .................................................................................................................................................. 15
Unattended Installation ................................................................................................................................. 16
FactoryTalk Directory .................................................................................................................................. 16
ProCalV5 Installation ................................................................................................................................... 17
FactoryTalk AssetCentre Client with 3rd Party Editor Integration ............................................................... 17
FactoryTalk AssetCentre SSL Protocol........................................................................................................ 17
FactoryTalk AssetCentre Windows Authentication Mode........................................................................... 18
FactoryTalk AssetCentre Web Client SSL Certificate ................................................................................. 18
FactoryTalk AssetCentre and Internet Protocol Security ............................................................................. 18
Upgrading a FactoryTalk AssetCentre System ............................................................................................ 19
Deploying a Configured FactoryTalk AssetCentre System ......................................................................... 19
Recommended System Limits .......................................................................................................................... 19
Activation/Licensing ........................................................................................................................................ 20
FactoryTalk Activation ................................................................................................................................. 20
Managing FactoryTalk AssetCentre Asset Capacity Totals ......................................................................... 21
MSSQL Server Licensing............................................................................................................................. 21
IIS Configuration .............................................................................................................................................. 21
FactoryTalk AssetCentre Virtual Directories ............................................................................................... 21
Anonymous Access ...................................................................................................................................... 22
Database Considerations .................................................................................................................................. 23
Renaming the AssetCentre Database............................................................................................................ 23
Using Multiple Instances .............................................................................................................................. 23

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 3 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Backing up and Restoring AssetCentre Database ........................................................................................ 23

Asset Archive Size ....................................................................................................................................... 23
AssetCentreUser SQL User .......................................................................................................................... 24
Changing AssetCentreUser password information ...................................................................................... 24
Using MSSQL Server Express ..................................................................................................................... 24
Managing MSSQL Database Size ................................................................................................................ 25
Using MSSQL on Foreign (non-US) Operating Systems ............................................................................ 25
Modifying MSSQL Memory Consumption ................................................................................................. 25
Modifying MSSQL Growth Policy .............................................................................................................. 25
Changing the Location of an MSSQL Server............................................................................................... 26
MSSQL Server 32-bit versus 64-bit ............................................................................................................. 26
FactoryTalk AssetCentre Server....................................................................................................................... 27
Changing the FactoryTalk AssetCentre Server Name.................................................................................. 27
Calibration Management Always Installed .................................................................................................. 27
FactoryTalk AssetCentre Client ....................................................................................................................... 28
Design Mode Ability .................................................................................................................................... 28
RSLogix Software Needed for Custom Compare Options........................................................................... 28
Co-locating Clients with Agents .................................................................................................................. 29
Calibration Management Server and Client Components ............................................................................ 29
Working with Large Asset Trees .................................................................................................................. 29
FactoryTalk AssetCentre Web Client ........................................................................................................... 30
FactoryTalk AssetCentre Agent ....................................................................................................................... 31
Determining Number of Necessary Agents .................................................................................................. 31
Agent Groups................................................................................................................................................ 31
FactoryTalk AssetCentre AgentController Service ...................................................................................... 32
FactoryTalk AssetCentre Agent Service vs Application .............................................................................. 32
FactoryTalk AssetCentre Agent Application Behavior with Remote Desktop Services ............................. 32
Common RSLinx Classic Drivers ................................................................................................................ 32
Security-enabled RSLogix Programming Software ..................................................................................... 33
Secured Zones with CIP Security ................................................................................................................. 33
Audit & Event Logs.......................................................................................................................................... 34
Audit Log...................................................................................................................................................... 34
Event Log ..................................................................................................................................................... 34
Audit Providers ............................................................................................................................................. 34
Audit & Event Caching ................................................................................................................................ 35
Audit & Event Log Historical Reporting ..................................................................................................... 35
Audit & Event Log Management ................................................................................................................. 35
Receiving Audits & Events from a PanelView Plus .................................................................................... 36
Receiving Audits & Events from a Computer Member of the FactoryTalk Directory ................................ 36
Audits & Events Log TrendPro Integration ................................................................................................. 36
Custom Audits & Events with FactoryTalk View SE .................................................................................. 36
Event Log Export Utility .............................................................................................................................. 36
Archive ............................................................................................................................................................. 37
Archive Management ................................................................................................................................... 37
Version Incrementing ................................................................................................................................... 37
Maximum File Size ...................................................................................................................................... 37

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 4 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Manual File Check-in ................................................................................................................................... 37

Force Comments on Check-in ...................................................................................................................... 38
Archive Historical Reporting ....................................................................................................................... 38
Archive Binders ............................................................................................................................................ 38
Archive to Archive Compare........................................................................................................................ 38
Archive to Archive Compare Clean-up ........................................................................................................ 38
RSLogix 5000 / Studio 5000 Logix Designer Linking Files ........................................................................ 38
RSLogix 5000 / Studio 5000 Logix Designer Backup Files ........................................................................ 39
Archive Extractor ......................................................................................................................................... 39
FactoryTalk AssetCentre Disaster Recovery Capability .................................................................................. 40
Agent Software ............................................................................................................................................. 40
Task Execution ............................................................................................................................................. 41
VerificationAgent Service ............................................................................................................................ 41
Agent Architecture and Configuration – v5.0 and earlier ............................................................................ 41
Agent Architecture and Configuration – v6.0 and later ............................................................................... 41
Determining Necessary Number of Agents .................................................................................................. 41
Creating Disaster Recovery Schedules ......................................................................................................... 42
Archive Check-In with Disaster Recovery ................................................................................................... 42
Supported Controller ControlLogix Firmware Versions .............................................................................. 42
Support for Studio 5000 ............................................................................................................................... 42
Disaster Recovery through a ControlLogix Gateway .................................................................................. 43
Disaster Recovery on ControlLogix Assets ................................................................................................. 43
Disaster Recovery with ControlLogix Source Protection ............................................................................ 43
ControlLogix Change Detect ........................................................................................................................ 43
ControlLogix Change Detect Scheduled Task Creation .............................................................................. 44
ControlLogix Change Detect Capable Assets .............................................................................................. 44
ControlLogix Change Detect with L6x Controllers ..................................................................................... 44
PanelView Plus Disaster Recovery with Multiple Agents ........................................................................... 44
Disaster Recovery with Rockwell Automation Drives ................................................................................ 44
Rockwell Automation Drives Database Updates ......................................................................................... 45
Generic FTP Device Compatibility .............................................................................................................. 45
Generic FTP Custom Comparisons .............................................................................................................. 45
Disaster Recovery with Stratix Switches ..................................................................................................... 45
Disaster Recovery on Remote Computers .................................................................................................... 46
Using Disaster Recovery for Remote Computers on Locked Files .............................................................. 46
Disaster Recovery with FactoryTalk View Site Edition .............................................................................. 46
Disaster Recovery with the FactoryTalk Directory ...................................................................................... 48
Custom Device Configuration with Scripted Mouse Movements ................................................................ 48
Asset Inventory Management Disaster Recovery Schedules ....................................................................... 48
Asset Inventory Management with CIP Devices.......................................................................................... 49
Asset Inventory Management with PanelView Plus and MobileView assets .............................................. 49
Asset Inventory Management with SNMP Devices ..................................................................................... 49
Product Lifecycle Management with Asset Inventory ................................................................................. 50
FactoryTalk AssetCentre Calibration Management Capability ....................................................................... 51
Building a Process Device Asset Hierarchy ................................................................................................. 51
Process Device Naming ................................................................................................................................ 51

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 5 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

ProCalV5 Component Architecture Considerations .................................................................................... 52

Asset Links ................................................................................................................................................... 52
Calibration Management Windows Security Settings .................................................................................. 52
FactoryTalk AssetCentre Process Device Configuration Capability ............................................................... 53
FDT/DTM Technology ................................................................................................................................ 53
System DTM Management........................................................................................................................... 53
Client DTM Management............................................................................................................................. 54
DTM Support................................................................................................................................................ 54
Building a DTM network ............................................................................................................................. 54
Process Device Configuration Editing Lock ................................................................................................ 55
Field Edition ................................................................................................................................................. 55
Field Edition DTM Catalog .......................................................................................................................... 56
Field Edition vs Embedded PDC .................................................................................................................. 56
Clients Share Network Paths ........................................................................................................................ 56
General Asset Tree Best Practices .................................................................................................................... 57
Asset Tree Hierarchy Best Practices ............................................................................................................ 57
Asset Tree Reporting .................................................................................................................................... 57
Asset Tree Export/Import ............................................................................................................................. 57
FactoryTalk Security ........................................................................................................................................ 58
User-based Access to Containers ................................................................................................................. 58
FactoryTalk AssetCentre Agents w/Co-located Clients Using Editor Security ........................................... 58
Remote Desktop Services ................................................................................................................................. 59
Remote Desktop Services Server FactoryTalk Components........................................................................ 59
FactoryTalk Audits with Remote Desktop Services .................................................................................... 59
Time Synchronization ...................................................................................................................................... 60
System Redundancy ......................................................................................................................................... 60
RSMACC to FactoryTalk AssetCentre Conversions ....................................................................................... 61
RSMACC Database Migration ..................................................................................................................... 61
Additional Reference Links .............................................................................................................................. 62
Tricks and Tweaks ........................................................................................................................................ 62
Troubleshooting ............................................................................................................................................ 62
FactoryTalk AssetCentre .............................................................................................................................. 62
General ......................................................................................................................................................... 62

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 6 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Introduction
This document is a supplement to the FactoryTalk AssetCentre documentation that is installed with the
software. It is designed to make system developers aware of the fundamental best-practice guidelines for
designing and implementing a FactoryTalk AssetCentre application. While labeled as the most recent
version of FactoryTalk AssetCentre, this document contains information for every released version.

For more information on the Integrated Architecture and the FactoryTalk Services Platform, refer to
Integrated Architecture Real-Time Information and Control. For more information on FactoryTalk
AssetCentre, refer to Rockwell Software AssetCentre.

What’s New in this Document

Since the last version of this document (published February-2018), note the following major
additions/changes:
• What’s New in FactoryTalk AssetCentre v9.00 (CPR9 SR11)
• Internet Protocol Security, in the Installation Best Practices section
• Anonymous Access, in the IIS Configuration section
• FactoryTalk AssetCentre AgentController Service, in the Agent section
• Secured Zones with CIP Security, in the Agent section
• Receiving Audits & Events from a Computer Member of the FactoryTalk Directory, in the Audit &
Event Logs section
• Audits & Events Log TrendPro Integration, in the Audit & Event Logs section
• VerificationAgent Service, in the Disaster Recovery Capability
• Disaster Recovery for View SE, in the Disaster Recovery Capability section
• Disaster Recovery for Stratix, in the Disaster Recovery Capability section
• Configuration with Scripted Mouse Movements, in the Disaster Recovery Capability section
• Product Lifecycle Management, in the Disaster Recovery Capability section

Using this Document

This document is intended to be a starting point and reference guide for the design of FactoryTalk
AssetCentre systems. The structure of the document is as follows:

• General information on distributed applications (e.g., workgroup vs. domain questions)

• General information on necessary components of an AssetCentre system (e.g., MSSQL, IIS)
• Overview, installation and activation of the AssetCentre components
• Specific information on AssetCentre components (e.g., client)
• Specific information on AssetCentre capabilities (e.g., Disaster Recovery)
• General information on security
• Miscellaneous system information
• Quick reference links

Information is sorted by relevance to a specific component or capability, meaning some overlap may exist.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 7 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Document Naming Conventions/Abbreviations

Frequently throughout this document, the user will be directed to more information in the form of Answer
IDs. These are technical papers created by Rockwell Automation and posted on the Rockwell Automation
Knowledgebase, accessible here: http://www.rockwellautomation.com/knowledgebase/

Prerequisite Reading
The following FactoryTalk AssetCentre related document is installed with the product and should be
considered prerequisite reading for this document:

• FTAC-IN005E-EN-E: FactoryTalk AssetCentre Installation Guide (FTAC-InstallGuide.pdf)

It can also be found in the Rockwell Automation Literature Library.

When using the AssetCentre client, a link to this document can be found from the Help menu:

Note: In a default AssetCentre installation, the file launched by this link can also be found in
C:\Program Files\Rockwell Software\AssetCentre Server or C:\Program Files\Rockwell
Software\AssetCentre Client, depending on which component is installed.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 8 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Revision History
• Revision 1.0 (12/2008): Initial release for v2.21.00 (CPR9)
• Revision 1.1 (04/2009): Release for v2.31.00 (CPR9 SR1)
• Revision 1.2 (01/2010): Updated information for v2.31.01 (CPR9 SR2)
• Revision 1.3 (04/2010): Release for v3.00 (CPR9 SR2)
• Revision 1.3 (02/2011): Release for v4.00 (CPR9 SR3)
• Revision 1.4 (04/2012): Release for v4.10 (CPR9 SR5)
• Revision 1.5 (03/2013): Release for v5.00 (CPR9 SR6)
• Revision 1.6 (01/2015): Release for v6.00 (CPR9 SR7.1)
• Revision 1.7 (08/2015): Release for v6.10 (CPR9 SR7.4)
• Revision 1.8 (03/2016): Release for v7.00 (CPR9 SR8)
• Revision 1.9 (01/2017): Release for v7.10 (CPR9 SR9)
• Revision 2.0 (02/2018): Release for v8.00 (CPR9 SR10)
• Revision 2.1 (03/2019): Release for v9.00 (CPR9 SR11)

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 9 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

What’s New in FactoryTalk AssetCentre v9.00 (CPR9 SR11)?

FactoryTalk AssetCentre v9.00 supports the CPR9 SR11 platform. Detailed release information can be
found in the “What’s new” section of the Release Notes. The Release Notes are available from the
FactoryTalk AssetCentre installation menu:

The Release Notes can also be found online at the Product Compatibility & Download Center site where the
user can customize the results with the desired information into a quick view or pdf report. A summary of
the new features and enhancements has also been included in this document:

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

Known Issues
Known issues can be found in the “Known Issues and Restrictions” section of the Release Notes.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 10 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

What’s New in FactoryTalk AssetCentre v8.00 (CPR9 SR10)?

FactoryTalk AssetCentre v8.00 supports the CPR9 SR10 platform. Detailed release information can be
found in the “What’s new” section of the Release Notes. The Release Notes are available from the
FactoryTalk AssetCentre installation menu:

After a default AssetCentre installation, the release notes can also be found at C:\Program Files\Rockwell
Software\AssetCentre Server\ReleaseNotes.htm or C:\Program Files\Rockwell Software\AssetCentre
Client\ReleaseNotes.htm, depending on the component installed. A summary of the new features has also
been included in this document:

• Automated Asset Lifecycle Status: FactoryTalk AssetCentre can now be configured to provide
asset life cycle information synchronized with the Product Compatibility and Download Center.
Assets can be scheduled for synchronization based on the asset tree or Asset Inventory Agent results.
• Disaster Recovery for Generic FTP Custom Compare: Compare Engines can now be configured
for use with Generic FTP Disaster Recovery tasks. Individual files retrieved as part of a scheduled
task can be configured for comparison in addition to the overall comparison of binary differences.
• Disaster Recovery for FactoryTalk Directories: A FactoryTalk Directory asset is now available
for Disaster Recovery operations. The FactoryTalk Directory asset is capable of backing up specific
applications (hierarchy only) or the entire directory, including security configurations.
• Asset Tree Import/Export Utility: The Import/Export utility now allows for multiple options of
importing and exporting the asset tree. Users can select full and partial exports, as well as automated
asset creation. Imported assets are not stripped of properties.
• Archive Cleanup Wizard update: The Archive Cleanup Utility now includes the option to clean up
historical archive comments. Comments can be exported, then permanently removed.
• Log Extractor: The Event Log Export Utility is available to system administrators for the purposes
of retrieving asset tasks reports in the event of AssetCentre server downtime.

Known Issues
Known issues can be found in the “Known Issues and Restrictions” section of the Release Notes.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 11 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Recommended Platform Requirements

The hardware and software used with FactoryTalk AssetCentre depends upon the demands of the
application, particularly with regard to the AssetCentre server. The greater the demand, the more powerful a
system is needed. For large or complex applications with high asset and archive needs, hosts with faster
CPUs and more RAM should be used for the server computer(s) (MSSQL and AssetCentre). In any
application, faster CPUs and more RAM will result in better performance.

In addition, there should always be sufficient disk space to provide virtual memory that is at least twice the
size of the physical RAM. The MSSQL server computer should also have ample disk space available, as the
database size will grow with use as more audit/diagnostic messages are logged and different file versions are
checked into the archive.

See the platform requirements in the FactoryTalk AssetCentre Installation Guide for specific information on
hardware and software requirements. For the latest information about the software platforms supported by
FactoryTalk AssetCentre, refer to the Product Compatibility and Download Center.
Note:
• Some Microsoft operating system service packs and hot fixes might not be compatible with
FactoryTalk AssetCentre. To find out if there are any problems with a particular Microsoft update
prior to applying it, refer to Answer ID 35530 – Microsoft Patch Qualification.
• FactoryTalk AssetCentre is tested on operating systems installed from original Microsoft media
only.

Windows Automatic Updates

It is recommended, but not required, that the Windows Automatic Updates feature be disabled.
Automatically applied patches could result in unpredicted behavior in a production system, such as
unplanned reboots and/or functionality changes. Manual patches can be applied after consulting Answer ID
35530 – Microsoft Patch Qualification.

Virtual Environments
Virtualization in a production environment is supported. For details on virtualization support, refer to
Answer ID 42682 – Rockwell Automation Software Compatibility Matrix.

Because each application is different, virtual sizing information (virtual machine configuration, host
resources, etc) is difficult to generalize. For more information on virtual sizing, refer to Answer ID 568026 –
Using Rockwell Automation Software with VMware and Virtualization for Process Automation Systems.

Internet Information Services (IIS)

Internet Information Services (IIS) is a required component for any computer acting as a FactoryTalk
AssetCentre server; it is not required for any other FactoryTalk AssetCentre computers (e.g., clients, agents,
etc.). When installing IIS, it is recommended to only install the minimum required components as described
in the ‘Installing Internet Information Services’ section of the FactoryTalk AssetCentre Installation Guide.
As of version 6.0, the FactoryTalk AssetCentre installation has become more automated. This automated
install will also configure IIS.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 12 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Windows Environment
FactoryTalk AssetCentre is supported in both domain and workgroup environments, where applications
consisting of 10 FactoryTalk computers or more require a domain. For more information on the differences
between a workgroup and a domain, refer to Answer ID 66173 - FactoryTalk Considerations for Windows
Workgroups and Domains.

Domain Best Practices

Extensive information on Microsoft domains is beyond the scope of this document, however there are some
key points that users of an AssetCentre system in a Windows Domain should understand:

• It is recommended to select internal Microsoft Active Directory domain names carefully. An internal
Microsoft Active Directory domain name should not be confused with an Internet (external) domain
name, and while they can be the same name, typically they are not.

• It is recommended to implement at least 2 domain controllers, where both are configured with the
Global Catalog (GC) role to provide high availability. By default, the GC role is only on the first
domain controller in the forest, but it is possible to add the GC role on other domain controllers from
the Active Directory Sites and Services console. Simply expand Sites > site name > Servers > server
name, right-click NTDS Settings, and select Properties. The Global Catalog check box is on the
General tab. Note: There are still a number of single instance domain controller roles that can result
in a single point of failure. These 5 Flexible Single Master Operations (FSMO) roles are:
1. PDC Emulator (one per domain)
2. Infrastructure master (one per domain)
3. Relative ID (RID) master (one per domain)
4. Schema master (one per forest)
5. Domain naming master (one per forest)

• It is recommended to configure time synchronization throughout a domain. For more information,

refer to the section entitled Time Synchronization later in this document.

• Rockwell Software does not support its software on computers configured as domain controllers.
The following information comes from a Microsoft TechNet article posted at
http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/security/secdefs.mspx.

The key sentence in this TechNote is "In general, Microsoft does not recommend running
applications on computers configured as domain controllers, and certainly not applications that
require more than Authenticated User privileges in order to run successfully." Installation of any
application software on a domain controller can have adverse effects on the network and is the
responsibility of the user to accept the risk.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 13 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Network Configuration
In depth network design is outside the scope of this document. For detailed information on configuring a
network, refer to the Ethernet Design and Implementation Guide. It’s important to note that any network
hosting FactoryTalk applications should use only managed switches.

WAN/Wireless Communications
Communications across anything slower than a 100mpbs, wired LAN can present negative impact on overall
system performance. Aside from the question of network security, which is outside the scope of the
document, two key factors are the speed and stability of the network. To mitigate problems due to signal
interference or timeouts, it is strongly recommended to use Remote Desktop Services to bridge any
WAN/Wireless communications. See the “Remote Desktop Services” section of this document for more
information on implementing Remote Desktop Services.

Firewall Communications
As the purpose of any firewall is to restrict port usage, a firewall should always be located at the entry/exit
point of a network. This will prevent outside access to the network, while allowing unimpeded internal
network communications.

If it is required to access a FactoryTalk system through a firewall, it is recommended to use Remote Desktop
Services (RDS.) RDS will require only one open port in the firewall, whereas FactoryTalk communications
will require many more, including the entire dynamic range of DCOM ports. See the “Remote Desktop
Services” section of this document for more information on implementing RDS, or see Answer ID 29402 -
TCP/UDP Ports Used by Rockwell Automation Products for a list of ports used by FactoryTalk.

Installation Best Practices

As of version 6.0, the FactoryTalk AssetCentre installation has become more automated, such that the three
main components (Server, Agent, Client) can be installed without constant user interaction. This automated
install will also configure IIS, install the FactoryTalk Services Platform, and install required support software
such as RSLinx Classic and FactoryTalk Linx.

The latest Rockwell Automation patches should always be applied to all relevant software packages. Patch
roll-ups and tables of contents can be located on the Rockwell Automation knowledgebase.

FactoryTalk Services Platform

FactoryTalk AssetCentre v9.00 (CPR9 SR11) has been fully tested and qualified with the FactoryTalk
Services Platform v6.11 (CPR9 SR11). While it is recommended to use v6.11 (CPR9 SR11) for new
installations, FactoryTalk AssetCentre is backwards-compatible with earlier versions of the FactoryTalk
Services Platform. See the Product Compatibility and Download Center for specific compatibility
information.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 14 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Component Architecture
Due to the distributed nature of the components of FactoryTalk AssetCentre, there are numerous possible
architectures for a given distributed system. For example, consider a small distributed system consisting of
the following components: FactoryTalk Directory (FTD), MSSQL, and FactoryTalk AssetCentre (FTAC)
server, agent, and client. This system could be deployed several ways using one or more hosts, here are just
2 examples:

1. Host #1 = FTD, MSSQL, FTAC server, FTAC agent, FTAC client, etc*
2. Host #1 = FTD, MSSQL, FTAC server; Host #2 = FTAC agent, FTAC client, etc*

*Note that any programming/communications software necessary for asset configuration/Disaster

Recovery operations would also need to be installed on this host.

Both of these examples show the MSSQL server installed on the same host as the FactoryTalk AssetCentre
server. While this is the most common scenario, it is not required. Each component mentioned above can be
located on its own computer, as in the example below:

• Host #1 = FTD; Host #2 = FTAC server; Host #3 = MSSQL; Host #4 = FTAC client, etc*;
Host #5 =FTAC agent, etc**

**Note that any programming/communications software necessary for Disaster Recovery operations
would also need to be installed on this host.

Servers are typically located in a secured, environmentally controlled area, while clients are typically in a
control room or on the plant floor.

Install Order
A FactoryTalk Network Directory server should be installed and configured first. If not already available, a
Microsoft SQL Server instance must also be installed and available.

When performing an installation that will make use of the Calibration Management capability, it is
recommended to install the ProCalV5 server prior to the FactoryTalk AssetCentre server. The ProCalV5
server installer creates the ProCalV5 database, which the FactoryTalk AssetCentre server installer prompts
for during the installation process.

Next, the FactoryTalk AssetCentre server must be installed prior to any FactoryTalk AssetCentre clients or
agents. If this step is skipped, the client/agent installation will fail to discover a suitable server within the
configured FactoryTalk Directory and the installation will abort.

The ProCalV5 client may be installed any time after the ProCalV5 server. Despite needing to be on the same
computer as an AssetCentre client, its installation is not dependent on having any of the FactoryTalk
AssetCentre software installed.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 15 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Unattended Installation
As of version 7.0, FactoryTalk AssetCentre offers four types of unattended installations:
• AssetCentre Server
• AssetCentre Client
• AssetCentre Agent
• Custom (all three components)

While the GUI will still appear on the target host, the unattended installation provides a number of
parameters to mitigate user interaction. In some cases, timeouts or error messages may prompt the user to
continue, requiring some interaction to proceed. For details, enter setup.exe /?.

FactoryTalk Directory
FactoryTalk AssetCentre makes use of a Network FactoryTalk Directory. The FactoryTalk Directory will be
used to provide and configure security options for FactoryTalk AssetCentre (as well as any other
FactoryTalk products in the directory). All components of the FactoryTalk AssetCentre system must belong
to the same Network FactoryTalk Directory to function correctly.

FactoryTalk Directory Server Location

The FactoryTalk AssetCentre server configures the FactoryTalk Directory with which its host is associated
upon installation. After the FactoryTalk AssetCentre server is installed, this configuration cannot be
performed manually on a “new” FactoryTalk Directory. Thus, it is important to decide on a configuration
that is likely to remain stable for the near future.

If a FactoryTalk AssetCentre server needs to be redirected to a FactoryTalk Directory that has never been
configured by a FactoryTalk AssetCentre server installation, a repair of the existing AssetCentre server will
be necessary (prior to version 2.74 of FTSP). The Server Configuration utility must then be launched.

In general, it is recommended that the FactoryTalk Directory Server be deployed on a separate, independent
host from other FactoryTalk AssetCentre components.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 16 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk Platform Compatibility

In a distributed FactoryTalk system, it is recommended that all computers are running the same FactoryTalk
Services Platform release. Ideally, this also includes the applicable patches.

An exception to this rule occurs in FactoryTalk Services Platform releases of CPR9: v2.10.00 (CPR9),
v2.10.01 (CPR9 SR1), v2.10.02 (CPR9 SR2), v2.30 (CPR9 SR3), v2.40 (CPR9 SR4), v2.50 (CPR9 SR5),
v2.60 (CPR9 SR6), v2.7x (CPR9 SR7.x), v2.80 (CPR9 SR8), v2.81 (CPR9 SR8.1), and v2.90 (CPR9 SR9).
Any of these releases can co-exist in a Network FactoryTalk Directory. Additionally, other Rockwell
Software products of the CPR9 releases can use the platforms interchangeably. For instance, FactoryTalk
AssetCentre v4.00 (CPR9 SR3) could also be installed on a computer with v2.40 (CPR9 SR4) of the
FactoryTalk Service Platform.

Despite this exception, it is recommended that all versions of the FactoryTalk Services Platform be
consistent over the entire Network FactoryTalk Directory. See Answer ID 58803 - Network FactoryTalk
Directory Best Practices for more information on setting up a FactoryTalk Directory.

ProCalV5 Installation
To provide the Calibration Management capability, Prime Technologies’ ProCalV5 is accessed and
configured using the FactoryTalk AssetCentre client. While the products are linked together, ProCalV5 is a
separate installation from FactoryTalk AssetCentre and uses a different database.

ProCalV5’s installation comes in two separate pieces, a server and a client. It is recommended to install the
ProCalV5 server on the same host as the FactoryTalk AssetCentre server. The ProCalV5 client must be
installed on a host with the FactoryTalk AssetCentre client, as there is no way to open the ProCalV5 client
except from within the FactoryTalk AssetCentre client itself.

FactoryTalk AssetCentre Client with 3rd Party Editor Integration

Starting in version 4.00, during the install for the FactoryTalk AssetCentre client, the user is given the option
to install integration components for Siemens editors. These integration components configure file
associations that allow the client to perform an “open” on Siemens programs from within the AssetCentre
client (a requirement for the automatic check-in feature) and require that the appropriate Siemens editor be
installed. If the editor is not installed during the client installation, the integration tools can be installed at a
later date by performing a client repair.

FactoryTalk AssetCentre SSL Protocol

In versions 7.10 and higher, FactoryTalk AssetCentre can be configured to use the SSL (Secure Sockets
Layer) protocol in a Windows domain environment. Enabling the SSL protocol will encrypt the
communications between the client/agent components and the FactoryTalk AssetCentre server. For more
information refer to the FactoryTalk AssetCentre Installation Guide, section “Configure the SSL protocol for
FactoryTalk AssetCentre” and Answer ID 1027507 - FactoryTalk AssetCentre SSL Protocol and Windows
Authentication Mode Setup.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 17 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre Windows Authentication Mode

In version 7.10 and higher, FactoryTalk AssetCentre can be configured to only use Windows Authentication
by denying access to anonymous users in a Windows domain environment. This prevents unauthorized users
from accessing the FactoryTalk AssetCentre server. For more information refer to the FactoryTalk
AssetCentre Installation Guide, section “Configure Windows Authentication” and Answer ID 1027507 -
FactoryTalk AssetCentre SSL Protocol and Windows Authentication Mode Setup.

FactoryTalk AssetCentre Web Client SSL Certificate

The FactoryTalk AssetCentre Installation Guide provides detailed information on how to create and install a
certificate for use with the Web Client. If no certificate is installed, the site may be treated as untrusted.

FactoryTalk AssetCentre and Internet Protocol Security

As of version 9.00 of FactoryTalk AssetCentre supports a network security architecture based on Internet
Protocol Security (IPSec) increasing network security by providing encryption, data integrity, and data
authentication. IPSec protects IP packets and defends against network attacks. Configuring IPSec on each
computer will send secure data between each other by using encryption, decryption, and data signing.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 18 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Upgrading a FactoryTalk AssetCentre System

Prior to any system upgrade, it is recommended that a backup of the AssetCentre database be performed. In
the event of a problem with the upgrade, the system can be reverted back to the backup version of the
database with minimal downtime. For additional information, see Answer ID 571530 – FactoryTalk
AssetCentre Upgrade Best Practices.

Deploying a Configured FactoryTalk AssetCentre System

Moving a FactoryTalk AssetCentre system from a previously configured location requires a number of steps,
including potential modifications of the FactoryTalk Network Directory, AssetCentre Database, etc. Refer to
Answer ID 548234 – Deploying a Pre-Configured FactoryTalk AssetCentre System for more information.

Recommended System Limits

Observe these limits, from the FactoryTalk AssetCentre reference architecture:
• The recommended maximum number of FactoryTalk AssetCentre concurrent clients that can have
simultaneous access to a FactoryTalk AssetCentre server is 100.
Note: Both FactoryTalk AssetCentre concurrent clients and computers with the FactoryTalk
Diagnostics Connector installation should count as part of the maximum recommended
number. The FactoryTalk Diagnostics Connector option is explained in a later section.
• The recommended, maximum tested number of FactoryTalk AssetCentre agents per server is 35.
• The recommended, maximum tested number of FactoryTalk AssetCentre agent groups is 35.
• The recommended, maximum tested number of FactoryTalk AssetCentre agents per agent group is 5.
• The necessary number of agents per server is dependent upon the number of assets to be serviced.
For estimation purposes, one agent is capable of servicing approximately 100 assets per 12 hours.
For detailed information, refer to Answer ID 106118 - Determining the Necessary Number of
FactoryTalk AssetCentre Agents.
• The maximum number of FactoryTalk AssetCentre servers per FactoryTalk Directory is 1. This
number cannot be exceeded.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 19 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Activation/Licensing
An electronic product activation tool, FactoryTalk Activation, is the primary activation means for
FactoryTalk AssetCentre. In FactoryTalk AssetCentre, the server is the only component that consumes
licenses. FactoryTalk AssetCentre clients and agents do not require activation. FactoryTalk AssetCentre
activation is based on two different categories: Capabilities and Capacity.

Capabilities are what the application is capable of performing, and currently falls into four categories:
Server, Disaster Recovery, Calibration Management, and Process Device Configuration. The FactoryTalk
AssetCentre server itself is required for any FactoryTalk AssetCentre installation. Disaster Recovery offers
several options, including Disaster Recovery for Rockwell devices, Remote Computers, and FTP Server, etc.

Capacity refers to either Asset Capacity or Agent Group Capacity. Asset Capacity determines how many
different devices a FactoryTalk AssetCentre installation is capable of servicing, and Agent Group Capacity
determines how many agent groups can be configured. A FactoryTalk AssetCentre server license comes
with 10 assets and 2 agent groups, meaning that up to 10 devices can be serviced and 2 agent groups
configured without any additional purchase. Beyond the initial counts, asset and agent group licenses are
additive (e.g., if another 25 asset count is purchased and used in conjunction with the existing 10 count, a
total of 35 assets can be serviced.)

Note: Asset Capacity activations are not needed for files, folders, and/or containers added to the
Asset Tree. Only Device assets (e.g., Logix5000 device, PLC5, etc.) added to the Asset Tree count
against the capacity activation.

FactoryTalk Activation
FactoryTalk Activation comes in two different types of configuration options for FactoryTalk AssetCentre:
• Capacity licensing uses concurrent activations
• Server and capability licensing uses node-locked activations

For more information regarding FactoryTalk Activation, including definitions of concurrent and node-locked
activations, refer to:
• the FactoryTalk Activation On-line Help
• Answer ID 35251 - FactoryTalk Activation Frequently Asked Questions
• FactoryTalk AssetCentre Time-Based Activation
• Answer ID 44623 - What Videos are available on FactoryTalk Activations?

If you plan to deploy a FactoryTalk Activation Server, refer to:

• the FactoryTalk AssetCentre Installation Guide: Installing FactoryTalk Activation, under Chapter 4
• Answer ID 41573 - FactoryTalk Activation End User Options File to Include/Exclude Borrowing
Activations
• Answer ID 35708 – How to support FactoryTalk Activations in a LAN/WAN Environment

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 20 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Managing FactoryTalk AssetCentre Asset Capacity Totals

Use the FactoryTalk AssetCentre Client to view the total number of assets utilizing capacity activation, as
well as the total asset capacity licensed. From Help -> About in the AssetCentre Client, select FactoryTalk
AssetCentre Server Features. See Asset Information -> Asset Licenses in use and/or Agent Group
Information -> Agent Group licenses in use

MSSQL Server Licensing

As of version 6.10 of FactoryTalk AssetCentre, new purchases of FactoryTalk AssetCentre server ship with
Microsoft SQL Server 2014 Express Edition. No licensing is required for this version of the product, but
customers should be aware of its limitations in contrast with Standard Edition:
https://www.microsoft.com/en-us/server-cloud/products/sql-server-editions/

In versions prior to v6.10, new purchases of FactoryTalk AssetCentre server shipped with a Single Processor
license includes access for an unlimited number of users or devices to connect from either inside or outside
the firewall. Customers did not need to purchase additional Server Licenses or client access licenses (CALs)
when licensed under this model.

More information on MSSQL licensing with regard to Rockwell Automation products can be found at
Answer ID 64647 – FAQ: Using Microsoft SQL Server with Rockwell Software FactoryTalk products.

IIS Configuration
IIS is required to be installed on the same host as the FactoryTalk AssetCentre server. Proper configuration
of IIS is critical to a successful FactoryTalk AssetCentre implementation, as all communication between
components (e.g., client to server communications) depends on IIS to some degree.

Note that as of v6.0, the AssetCentre server installation will automatically configure IIS if desired.

FactoryTalk AssetCentre Virtual Directories

Upon installation, the FactoryTalk AssetCentre server creates two virtual directories linked to the
FactoryTalk AssetCentre server installation folders. One Virtual Directory is specific to “thick” access by
AssetCentre Client and Agent computers, and one is specific to Web Clients. By default, these are
configured within the Default Web Site. If more than one website is configured at the time of installation,
the user will have the option to choose the preferred installation location.

The AssetCentre virtual directory must have execute permissions set to ‘Scripts Only.’ Having execute
permissions denied to the directory (selection set to ‘None’) will result in the server being unable to start
correctly, as IIS will be unable to execute necessary server-side DLLs.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 21 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Anonymous Access
The FactoryTalk AssetCentre virtual directory must be accessible via IIS anonymous access. If anonymous
access is not configured correctly, FactoryTalk AssetCentre clients will be unable to connect to the server.
When IIS is initially installed, by default, an IIS user is created named IUSR_<computer name> and
configured as the anonymous access user. This can be changed to a user defined user, but should not be a
domain-authenticated user.

The anonymous user must have read, read & execute, and list folder permissions to the virtual directory. By
default, the virtual directory inherits the folder permissions set on the windows folder it is linked to (in this
case, the FactoryTalk AssetCentre server folder). By default, this access is granted in the form of the local
computer’s Users group, which contains the IUSR. If special security settings have been enforced, or if the
anonymous access user has been changed, these access privileges will need to be confirmed.

Finally, the anonymous access user must have the ‘Access this computer from the network’ right, which is
found under User Rights Assignment in Local Security Policies. This right can be pushed down and locked
via a domain policy, thus overriding the default workstation configuration.

It is possible to leverage Windows Authentication mode as another form of access, which was introduced in
7.10. Windows Authentication provides a secure form of authentication where the user name and password
are hashed before being sent across the network making the system more secure. The AssetCentre system
can be configured to only use Windows Authentication by denying access to anonymous users in a Windows
Domain environment. This prevents unauthorized users from accessing the FactoryTalk AssetCentre server
by only allowing access via Windows Authentication. For more information refer to the FactoryTalk
AssetCentre Installation Guide, section “Configure Windows Authentication” or Answer ID 1027507 -
FactoryTalk AssetCentre SSL Protocol and Windows Authentication Mode Setup.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 22 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Database Considerations
Microsoft SQL (MSSQL) Server is a required component for any FactoryTalk AssetCentre implementation.
While it is not required to be installed on the same host as any FactoryTalk AssetCentre component, many
architectures have it co-located on the same host as the FactoryTalk AssetCentre server. FactoryTalk
AssetCentre supports Express, Standard, and Enterprise editions.

An existing MSSQL server may be used for FactoryTalk AssetCentre, and the server does not need to be
dedicated to FactoryTalk AssetCentre alone (i.e., it can hold databases for multiple applications.) If a new
installation will be used, refer to the steps described in the ‘Installing Microsoft SQL Server’ sections of the
FactoryTalk AssetCentre Installation Guide.

When the FactoryTalk AssetCentre server is installed, the AssetCentre database is created in the chosen
MSSQL server. In addition to the database, the AssetCentreUser SQL user and AssetCentreUser schema are
created. The database creation is an on-installation only event, meaning that the desired MSSQL server
should be identified prior to AssetCentre server installation. Note that remote connections to the server must
be enabled for the installation of the FactoryTalk AssetCentre database.

Renaming the AssetCentre Database

While it is possible to rename the FactoryTalk AssetCentre database from the default ‘AssetCentre,’ it is not
recommended. In particular, all upgrade scripts are hard-coded to look for the ‘AssetCentre’ database,
meaning that if it has been renamed, it must be named back to the default prior to any upgrades taking place.

Using Multiple Instances

In some configurations, it may become desirable for a number of different FactoryTalk AssetCentre servers
to utilize the same MSSQL server. Because renaming the ‘AssetCentre’ database is not recommended, the
next option would be to use multiple MSSQL server instances running on the same host (thereby saving
hardware cost,) thus allowing the different instances to each host an AssetCentre database. While this
configuration is supported, it is not recommended. The recommended solution is to always use a single
MSSQL server instance on a single MSSQL server host per AssetCentre server. See Answer ID 54520 -
Using multiple FactoryTalk AssetCentre Servers with multiple instances of SQL Server on a single host for
more information on this architecture.

Backing up and Restoring AssetCentre Database

The whitepaper located at Answer ID 59541 - Backing up and Restoring FactoryTalk AssetCentre with
Microsoft SQL Server is designed to assist MSSQL database administrators with the procedure of backing
up the AssetCentre database, and in the event of an unlikely system failure, quickly restoring that backup to
minimize down time.

Asset Archive Size

As of version 6.10, each individual asset’s archive view will show its disk consumption as well as its total
number of versions. Prior to 6.10, refer to Answer ID 638811 – FactoryTalk AssetCentre Asset Size View
for sample Microsoft SQL queries that will report on asset sizes.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 23 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

AssetCentreUser SQL User

The AssetCentreUser SQL user is created during the installation of the FactoryTalk AssetCentre server and
subsequent creation of the AssetCentre database. The installation program will prompt the user for a
Username and Password after the creation of the database itself. This account is used internally by the
FactoryTalk AssetCentre server to connect to the SQL database; it is never interactively used by any client or
agent on the system. Finally, this account is created as a SQL account; a windows or active directory linked
account is not usable.

The user is given public rights to the server, along with db_dataread, db_datawrite, db_dataexecute rights to
the AssetCentre database. The db_dataexecute right is also created at this time to give the user rights to
execute stored procedures in the AssetCentre database. Finally, the AssetCentreUser schema is also created
and assigned to the user. The user is not only assigned the schema, but is also the schema owner.

Changing AssetCentreUser password information

It is possible to change the password of the AssetCentreUser after installation. This should not be attempted
using the MSSQL server administration tools (e.g., Enterprise Manager). Instead, launch the Data Source
Configuration Wizard, which is installed on the server computer under Program Files -> Rockwell Software
-> FactoryTalk AssetCentre server. This utility will allow the user to change the password referenced by
AssetCentre, as well as the SQL user itself, at the same time.

Using MSSQL Server Express

As of version 6.10, FactoryTalk AssetCentre supports using MSSQL Server Express. MSSQL Server
Express has a number of limits compared to the Standard version that should be assessed before making a
decision for the application in question. For more information on limitations and FactoryTalk AssetCentre
database usage, refer to Answer ID 942093 – FactoryTalk AssetCentre and Microsoft SQL Server Express
support.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 24 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Managing MSSQL Database Size

As the MSSQL database size grows, more resources on both the FactoryTalk AssetCentre client and server
computers are used. As of version 6.10, FactoryTalk AssetCentre can be configured to automatically
monitor the size of the database and its various components, including total size, diagnostic log sizes, and
archive version totals. It is strongly recommended to use this feature in conjunction with the manual cleanup
tools such as Archive Cleanup and Log Cleanup wizards (see sections on these later in this document.) Refer
to Answer ID - FactoryTalk AssetCentre Database Management and Answer ID 728263 – FactoryTalk
AssetCentre Database Management FAQs for more information.

It is also recommended to monitor the size of the transaction logs. Particularly in systems that have
constantly changing data like FactoryTalk AssetCentre, these logs tend to grow very quickly. Where
possible, set the database's recovery mode to simple and perform Full backups as part of the system backup
plan, which will allow for the scheduled shrinking of these logs. Other scheduled operations should include
indexing and free space cleanup operations. The exact implementation of these policies should be
determined by the end user’s database management team.

For information on how the database size impacts client and server performance, see the Working with Large
Asset Trees subsection of the FactoryTalk AssetCentre Client section.

Using MSSQL on Foreign (non-US) Operating Systems

On non-English (US) operating systems, it is possible for a discrepancy in the default language of the
MSSQL users used by FactoryTalk AssetCentre and the OS language to prevent the FactoryTalk
AssetCentre server service from starting correctly. The steps at Answer ID 60781 - Using FactoryTalk
AssetCentre with Foreign Operating Systems and MSSQL Default Languages walk through how to check
the languages, as well as how to rectify any discrepancy.

Modifying MSSQL Memory Consumption

When FactoryTalk AssetCentre is installed on the same server as the Microsoft SQL Server, setting a 'Max
Server Memory' value for the Microsoft SQL Server is highly recommended. This will ensure that the
memory required by the Rockwell Software applications is not completely consumed by the SQL Server.
For more information on how to accomplish this, refer to Answer ID 64647 - FAQ: Using Microsoft SQL
Server with Rockwell Software FactoryTalk Products.

Modifying MSSQL Growth Policy

Consider expanding on the database's growth policy, particularly in larger systems that will be dealing with
large amounts of data over small periods of time. A small growth policy may prevent the database from
expanding sufficiently, which may result in database communication errors.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 25 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Changing the Location of an MSSQL Server

During the installation of FactoryTalk AssetCentre, a database is selected and configured. After installation,
it may be desirable to change the database that the software is using. This can be accomplished using the
Data Source Configuration utility, found on the FactoryTalk AssetCentre server.

Prior to running the Data Source Configuration wizard, the new database must be configured to match the
existing one. While the installation of FactoryTalk AssetCentre does this automatically, the Data Source
Configuration wizard does not, so it must be done manually. The attached document located at Answer ID
46644 - Configuring FactoryTalk AssetCentre to use a different SQL database walks through the required
process.

MSSQL Server 32-bit versus 64-bit

FactoryTalk AssetCentre supports both 32 and 64-bit versions of MSSQL Server 2012 and 2008. Versions
of FactoryTalk AssetCentre prior to v5.0 in use with ProCalV5 (used with the Calibration Management
capability) require 32-bit only. Version 5.0 of FactoryTalk AssetCentre in use with ProCalV5 will require
the modification detailed in Answer ID 499769 – Microsoft SQL for 64-bit processors with FactoryTalk
AssetCentre. Versions 6.0 and higher natively support ProCalV5 with 64-bit Microsoft SQL.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 26 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre Server

A FactoryTalk AssetCentre server is required for any installation of FactoryTalk AssetCentre. The server is
configured using the FactoryTalk AssetCentre client, and provides the Archive and Audit/Event Log
functionality. The FactoryTalk AssetCentre server is also responsible for managing any scheduled tasks, and
assigning the tasks to the FactoryTalk AssetCentre agents. The FactoryTalk AssetCentre server must have
connectivity to Microsoft SQL Standard database, which is used by the FactoryTalk AssetCentre server to
store all pertinent FactoryTalk AssetCentre information.

There can be only one FactoryTalk AssetCentre server in an architecture, and a FactoryTalk AssetCentre
server must belong to only one FactoryTalk Network Directory. A FactoryTalk Network Directory may
have no more than one FactoryTalk AssetCentre server associated with it. This architectural consideration is
often overlooked, with designers attempting to include more than one FactoryTalk AssetCentre server in a
single FactoryTalk Directory. See Answer ID 58052 - Number of FactoryTalk AssetCentre Servers Needed.

The FactoryTalk AssetCentre server host may have a co-located FactoryTalk AssetCentre client and/or
agent, and may also have an installation of Microsoft SQL Standard co-located.

Changing the FactoryTalk AssetCentre Server Name

Changing the computer name alone will not update the FactoryTalk Directory server, resulting in
clients/agents unable to connect. Use the Configure Server Settings application (installed with FactoryTalk
AssetCentre server) to reset FactoryTalk Directory pointer after name change. This will ensure that the
FactoryTalk Directory knows the new computer name.

These steps assume that the appropriate measures have been taken if the SQL server is co-located with the
FactoryTalk AssetCentre server. See Microsoft documentation for name changes if the MSSQL server is co-
located.

Calibration Management Always Installed

The Calibration Management piece of FactoryTalk AssetCentre server (not ProCalV5 itself) is always
installed by default, whether the capability is purchased or not. It is required to proceed with this
installation, even if there are no future plans to use the Calibration Management functionality.

The configuration utility has a ‘Skip’ button at the top, which allows the user to skip the configuration of the
component and should be used if ProCalV5 is not already installed. Installing this piece allows for the
capability to be used at a later time, if desired, despite not having the capabilities activated right away.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 27 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre Client

FactoryTalk AssetCentre clients are required to configure and communicate with the FactoryTalk
AssetCentre server, including configuring and performing searches and Disaster Recovery schedules, as well
as checking files into and out of the archive. There can be up to 50 concurrent clients in an architecture
(recommended). FactoryTalk AssetCentre clients may be co-located with the FactoryTalk AssetCentre
server and/or agents. FactoryTalk AssetCentre clients may also be installed on hosts with other Rockwell
Software products installed, so long as the CPR (Coordinated Product Release) versions of each product
packages’ FactoryTalk Services Platform are compatible.

The FactoryTalk AssetCentre client host will also need to have the appropriate communications software
(e.g., FactoryTalk Linx, RSLinx Classic) installed based on the assets configured within the system. Only
the configured asset communication software needs to be installed; un-configured assets do not require
software (e.g, FactoryTalk Linx does not need to be installed if Disaster Recovery will not extend to
PanelView Plus assets.) The communications software does not need to be activated to work with
FactoryTalk AssetCentre.

Design Mode Ability

FactoryTalk AssetCentre clients are used to administer the database, as well as interact with the Event/Audit
logs and Archive. Part of the clients’ administrative duties include configuring the Asset Tree, which is a
hierarchical model containing all assets.

When an asset is configured, its network path is input, tying the FactoryTalk AssetCentre asset to the real-
world device. This path is used for any further communications to the asset, including Disaster Recovery
schedules, and includes the RSLinx driver name (e.g., AB_ETH-1) and the network address (e.g., IP address)
of the physical device. As such, the client configuring the asset must be using the exact same path as any
subsequent FactoryTalk AssetCentre components, particularly the FactoryTalk AssetCentre agents.

In many architectures, it is not feasible to require all clients to have the same access path to all assets as the
agents of the system. Thus, it could be advisable is to restrict design mode access to only the clients that will
be used for configuration purposes. Those with different access paths, then, will be unable to accidentally
change any asset properties while still being able to interact with the Archive and Audit/Event logs.

RSLogix Software Needed for Custom Compare Options

Users should be aware that the configuration software for RSLogix assets is required when using the
FactoryTalk AssetCentre client to configure a custom compare (RSLogix 5 & 500 assets) and/or tag filtering
(RSLogix 5000) in Disaster Recovery. The configuration software is used to access the program file to
provide the comparison options, resulting in an error if not installed.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 28 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Co-locating Clients with Agents

It is generally not recommended to co-locate the FactoryTalk AssetCentre client with the FactoryTalk
AssetCentre agent for anything other than design purposes. Since the FactoryTalk AssetCentre agent will
have system resources utilized at random when executing schedules, this can make utilizing the same
computer as a workstation difficult.

Since all assets must be configured in the asset tree by a FactoryTalk AssetCentre client, the FactoryTalk
AssetCentre client must have the same RSLinx Classic driver names and paths to the assets as the agents.
With this in mind, co-locating a FactoryTalk AssetCentre client with a FactoryTalk AssetCentre agent for the
purposes of configuring the asset tree can be beneficial. See Answer ID 58050 - Co-locating FactoryTalk
AssetCentre Client and Agent Components for more information.

Calibration Management Server and Client Components

The FactoryTalk AssetCentre Calibration Management client piece (not ProCalV5 itself) is installed by
default as part of the FactoryTalk AssetCentre client installation, whether the capability is intended for use or
not. Installing this piece allows for the capability to be used at a later time, if desired, despite not having the
capabilities activated right away. This component should not be uninstalled independently of the
FactoryTalk AssetCentre client component.

Working with Large Asset Trees

When a FactoryTalk AssetCentre client is launched, the client requests the entire asset tree structure and key
properties of each asset from the FactoryTalk AssetCentre server. In large asset trees (e.g., approaching and
greater than 100,000 assets, including files), this process can introduce a noticeable lag for the client to fully
load. The most critical system resource during this time is the amount of memory present on both the server
and client hosts.

Collapsing sections of the asset tree that are not frequently used can decrease the amount of time needed for
a FactoryTalk AssetCentre client to finish loading. The fewer hierarchical levels and overall assets pictured
in the tree at loading, the less amount of time needed.

See Answer ID 106054 - Working with Large Asset Trees in FactoryTalk AssetCentre for more information,
as well as memory recommendations.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 29 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre Web Client

The FactoryTalk AssetCentre Web client requires no installation, instead accessing the server through an
internet browser. The web client can be run on a computer, or on a mobile device (e.g., smart phone). The
web client can be accessed at http://<FTAC-server-name>/RockwellSoftware/AssetCentreMobileClient, with a
recommended maximum of 50 simultaneous web clients connecting to a single server.

The web client can be used to view information about the FactoryTalk AssetCentre system, and can also
execute scheduled tasks such as searches and Disaster Recovery operations. As of version 7.0, there is are
no write capabilities, meaning that no archive options (check-in, check-out) or asset tree manipulation are
possible.

Client performance is based on the number of web clients simultaneously requesting information from the
server, and the size of the AssetCentre system. As the number of assets, schedules, etc grow, additional time
will be required to process each client request.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 30 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre Agent

FactoryTalk AssetCentre agents are required in all FactoryTalk AssetCentre applications, regardless of the
user of Disaster Recovery. As of v6.0, there can be up to 15 agents in any architecture. FactoryTalk
AssetCentre agents may be co-located with the FactoryTalk AssetCentre server and/or clients (client co-
location recommended for configuration purposes only).

Note: It is possible to exceed 15 agents in a single system, but doing so is not recommended.
Because the maximum number of agents used in product testing was 15, exceeding this number will
introduce some risk, as this configuration has not been thoroughly tested.

The FactoryTalk AssetCentre agent host will need to have the appropriate communications software (e.g.,
FactoryTalk Linx, RSLinx Classic) and asset configuration software (e.g., RSLogix, FactoryTalk View
Studio, Drive Executive) installed based on the assets configured within the system. Only the configured
asset configuration and communication software needs to be installed, un-configured assets do not require
software (e.g., FactoryTalk Linx and FactoryTalk View Studio do not need to be installed if Disaster
Recovery will not extend to PanelView Plus assets.) The communications and configuration software does
not need to be activated.

See Answer ID 58049 - FactoryTalk AssetCentre Agent FAQ for more information on agents.

Determining Number of Necessary Agents

FactoryTalk AssetCentre uses agents to perform scheduled tasks, such as scheduled searches of the audit
logs and backups of assets such as ControlLogix processors. If a system is not using the Disaster Recovery
capability, scheduled searches will be the only function that requires the FactoryTalk AssetCentre agent.
Many architectures will find need for only a single agent, oftentimes co-located with the FactoryTalk
AssetCentre server.

See the section of this document on Disaster Recover for more information on how many FactoryTalk
AssetCentre agents are required for systems using the Disaster Recovery capability.

Agent Groups
As of version 6.0, FactoryTalk AssetCentre Agents may be categorized into groups. By default, and in
versions prior to 6.0, all Agents were required to be identically configured such that the AssetCentre Server
could assign a task to any existing Agent. With Agent Groups, an asset can have an assigned Agent Group,
allowing for Agents to have different configurations. Up to 10 Agent Groups can be configured on a given
system, and up to 5 Agents can be configured per group. A single Agent may be a member of multiple
groups. See Answer ID 632852 – FactoryTalk AssetCentre Agent Group FAQ for more information.

Note: It is possible to exceed 10 agent groups in a single system, but doing so is not recommended.
Because the maximum number of agent groups used in product testing was 10, exceeding this
number will introduce some risk, as this configuration has not been thoroughly tested.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 31 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre AgentController Service

As of version 9.00 of FactoryTalk AssetCentre, the Agent Service Logon Configuration tool will only update
the VerificationAgent service logon as the AgentController requires the service to be logged on as Local
System. The AgentController requires the service to be logged on as Local System for Disaster Recovery
operations of a FactoryTalk View SE asset.

FactoryTalk AssetCentre Agent Service vs Application

The FactoryTalk AssetCentre Agent application, introduced in version 6.10, is designed to run with the
privileges of the currently logged-in session, including desktop interaction. The AgentController service
runs in session 0, which uses the security privileges of the service’s configured user, but is unable to interact
with the desktop. The application and service cannot run simultaneously. Use the FactoryTalk AssetCentre
Agent Launch Control Panel to manage the agent (see Answer ID 728265 – FactoryTalk AssetCentre Agent
Launch Control Panel).

FactoryTalk AssetCentre Agent Application Behavior with Remote Desktop Services

A single agent can be located on a single physical host. When the agent is operating as an application, it is
possible for multiple remote desktop sessions to run one agent application apiece, but this is not a supported
architecture.

Common RSLinx Classic Drivers

If using the RSLinx Classic communications software (e.g., if performing Disaster Recovery operations on a
Logix5000 device), all Agents participating in the same Agent Group must use common RSLinx Classic
Drivers. The FactoryTalk AssetCentre Client used to configure the Agent Group must also use the same
RSLinx Classic configuration.

When a FactoryTalk AssetCentre client is used to configure an asset, the communications path to the asset is
configured using the corresponding path on the client computer (e.g., AC_SERVER!AB_ETH-
1\131.200.172.20\Backplane\0). This driver name (and asset path) must match on each RSLinx Classic
instance for the asset communications to work correctly. Note that the host name is not part of this
requirement, as each host name will be different.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 32 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Security-enabled RSLogix Programming Software

If FactoryTalk Security is enabled in RSLogix programming software (RSLogix 5, RSLogix 500, or
RSLogix 5000), the Disaster Recovery agent and FactoryTalk Security must be properly configured to grant
the necessary permissions for Disaster Recovery operations.

Note: As of v20 of RSLogix 5000, security is enabled “out of the box,” meaning that these
FactoryTalk AssetCentre configurations are required.

In short, a local user account must be configured to run the FactoryTalk AssetCentre disaster recovery
service. This account must also be added to FactoryTalk Security as a windows-linked user and given at
least read-access to the FactoryTalk Directory, as well as RSLogix-specific privileges. In versions prior to
5.0, or if using RSLogix v16 or earlier, single sign-on must be enabled in FactoryTalk Security.

For a complete walkthrough of the configuration process, refer to the ‘Configuring for security-enabled
RSLogix programming software’ section of the FactoryTalk AssetCentre Installation Guide.

Starting with v4.10, the “Agent service logon config tool” will automatically perform these configurations.
This utility is installed by default, and can be found under the FactoryTalk AssetCentre Agent from Start.

Secured Zones with CIP Security

As of version 9.00, FactoryTalk AssetCentre adopts FactoryTalk Linx Enterprise, which enables Disaster
Recovery operations of devices that are members of a CIP Security secured zone. For example,
ControlLogix controller version 32 and higher.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 33 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Audit & Event Logs

The FactoryTalk AssetCentre server provides Audit and Event log functionality without any additional
capability licensing. Audit & Event logs tie directly into the FactoryTalk Services Platform to receive
information from diagnostic-enabled pieces of FactoryTalk software, including FactoryTalk View, RSLogix
5000, and FactoryTalk AssetCentre itself.

Audit Log
The Audit Log displays information regarding user actions performed in the system, such as making edits to
an RSLogix 5000 project or checking out a file from the FactoryTalk AssetCentre database. Audits can
originate from any piece of FactoryTalk software, and include the time the action was logged, from which
program it was logged, from which host it was logged, and which user performed the action.

An example of an audit would be a user going online with a ControlLogix processor and making changes. In
this example, the FactoryTalk AssetCentre server would receive audits for the user going online with the
controller, as well as each edit made (e.g., creating a tag, deleting a rung, etc).

Event Log
The Event Log displays information regarding events that occur in the system. Events are generally system
initiated (e.g., a server came online or a scheduled task completed.) Event records can originate from any
piece of FactoryTalk software, and include the time the action was logged, from which program it was
logged, and from which host it was logged.

An example of an event would be a piece of FactoryTalk software checking out an activation from an
Activation server, and would include the specific information on the activation name, serial number, and
type checked out.

Audit Providers
If FactoryTalk AssetCentre is installed in a system with other FactoryTalk Audit enabled software pieces
(such as View SE), it is possible to receive audit messages from them. In order to receive these Audits, it is
necessary to install the FactoryTalk AssetCentre client on any computers hosting these software pieces. The
FactoryTalk AssetCentre client is responsible for collecting the audit and event messages locally, then
passing them on to the FactoryTalk AssetCentre server. See Answer ID 59542 - FactoryTalk AssetCentre
Client Needed to Receive Audits for more information.

Exempt from this rule are Windows CE based components, such as View ME applications running on
PanelView Plus devices. See the section below on receiving audits and events from a PanelView Plus for
more information on this.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 34 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Audit & Event Caching

If a situation occurs where the FactoryTalk AssetCentre server is offline for a period of time, audit and event
messages are not lost. The FactoryTalk AssetCentre client will cache all log messages from the local
computer, then push the messages up to the AssetCentre server when a connection is re-established. The
cache limitation is 4GB. The FactoryTalk AssetCentre client does not need to be active (i.e., open) for the
cached logs to be sent to the server.

In versions prior to v6.00, if a long-term absence of connection to the FactoryTalk AssetCentre server
occurs, it is possible for this cache file to grow too large to synchronize using the default connection. See
Answer ID 586038 - RSVCHOST Consuming 50-90% Processor on FactoryTalk AssetCentre Client for a
resolution. v6.00 of FactoryTalk AssetCentre resolves this problem.

Audit & Event Log Historical Reporting

It may be desirable to perform historical reporting on FactoryTalk AssetCentre audit and event logs, outside
of the searching capabilities present in the FactoryTalk AssetCentre client. While the client offers searching
capabilities natively, broader queries can be accomplished using SQL Server. A SQL Server script provided
by Rockwell Automation can be used to install a set of SQL Server views into the AssetCentre database on
the system’s SQL Server, which can be used to query and potentially export audit, event, and/or network
health and diagnostics logs.

To download the SQL Server script and read more about the capabilities and usage of this SQL Server View,
see Answer ID 58298 - Historical Reporting on FactoryTalk AssetCentre Audit and Event Logs.

Audit & Event Log Management

Through the course of normal operation, the Audit and Event logs of the FactoryTalk AssetCentre system
can grow quite large. As a direct consequence, the MSSQL database size will also expand. Due to these
considerations, it is recommended for an administrator of the system to back up and delete older log
messages.

The Log Cleanup Wizard can be found from the Tasks menu, and will allow the user to edit the Event, Audit,
and/or Diagnostics log. This utility will delete log messages from the beginning of the log (i.e., the earliest
recorded messages) to a user-defined point, with the selected logs capable of being exported prior to
deletion. These exported logs can be viewed using the FactoryTalk AssetCentre Exported Log Viewer,
found from Programs -> Rockwell Software -> FactoryTalk AssetCentre Client.

In version 6.00 of FactoryTalk AssetCentre, the Log Cleanup Wizard functionality can be accessed from a
command line, enabling its scheduled operation using a Windows Scheduled Task. This functionality is also
available in versions 5.00 and 4.10 via the latest patches. For more information, see Answer ID 586569 -
Using the FactoryTalk AssetCentre Log Clean-up Wizard from a Command Line.

Finally, if large audit and/or event log tables cannot be avoided, consider using the indexing script at Answer
ID 79396 - FactoryTalk AssetCentre Audit and Event Log Performance Indexing. The script can take a
significant amount of time to execute on large tables, but will also improve query performance.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 35 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Receiving Audits & Events from a PanelView Plus

Since PanelView Plus (and PanelView Plus CE) devices are based on a Windows CE operating system, it is
not possible to install the FactoryTalk AssetCentre client on them to directly receive audit messages. Using
FactoryTalk Diagnostics remote logging, however, it is possible to direct the PanelView Plus device’s
messages (both audits and events) to a remote FactoryTalk AssetCentre Client.

Each PanelView Plus device on the network can be configured to direct its audits and events to a desktop or
server host via network connectivity. The FactoryTalk AssetCentre client on this host will then capture the
messages and forward them on to the FactoryTalk AssetCentre server as any other message. Any audits
and/or events generated from the PanelView Plus device will show the PanelView Plus device’s name and
user (as opposed to information of the PC to which the messages are directed). See Answer ID 58977 -
Using FactoryTalk AssetCentre to Receive Audits from a PanelView Plus for more specific instructions on
configuring this functionality.

Receiving Audits & Events from a Computer Member of the FactoryTalk Directory
As of version 9.00 of FactoryTalk AssetCentre, diagnostic information (audit and event logs) can be
collected from computers that are part of the FactoryTalk Directory where FactoryTalk AssetCentre is
configured without having to install the FactoryTalk AssetCentre client. This is possible by installing the
FactoryTalk Diagnostics Connector option, which installs the FactoryTalk AssetCentre common components
responsible for driving diagnostic information into the FactoryTalk AssetCentre system from computers
without the FactoryTalk AssetCentre client. Computers from which diagnostics information collection is
desired must be part of the FactoryTalk Directory where FactoryTalk AssetCentre is configured. For more
information, refer to Answer ID 1083668 – FactoryTalk AssetCentre Diagnostics Connector.

Note: As a general recommendation, both FactoryTalk AssetCentre concurrent clients and computers
with the FactoryTalk Diagnostics Connector installation should count as part of the maximum
recommended limit.

Audits & Events Log 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.

Custom Audits & Events with FactoryTalk View SE

Using VBA scripting in FactoryTalk View SE, it is possible to customize audit (and event) diagnostic
messages, such that specific actions outside of default can be recorded. For more information, see Answer
ID 493306 - Using FactoryTalk View SE with FactoryTalk AssetCentre.

Event Log Export Utility

The Event Log Export Utility is available to system administrators for the purposes of retrieving asset task
reports in the event of AssetCentre server downtime. The Event Log Export Utility will connect directly to
the AssetCentre database to export the reports associated with the last run status of each Disaster Recovery
task.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 36 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Archive
FactoryTalk AssetCentre server provides the Archive capability without any additional capability licensing.
The Archive provides back-up and version control for any type of computer files (i.e., not restricted to
Rockwell Automation files.) While this functionality is provided through the FactoryTalk AssetCentre
server, the FactoryTalk AssetCentre client is used to administer the archive, and the actual files checked into
the archive are stored in the MSSQL database.

Archive Management
The FactoryTalk AssetCentre client can be used to run the Archive Cleanup Wizard, which will assist the
user in deleting any old/unnecessary file versions stored in the FactoryTalk AssetCentre Archive. Version
numbers will not be edited for newer file versions, and a record of the deleted version(s) will be kept, but the
space used in the MSSQL Database will be freed up. The Archive Cleanup Wizard is also accessible from a
command line, enabling its scheduled operation using a Windows Scheduled Task.

As of version 6.10, each archived asset can have a maximum number of versions specified. Using this
functionality, FactoryTalk AssetCentre will automatically delete the oldest version (excluding version 1)
when a new version is checked in that would put the asset over the maximum setting.

As of version 8.0, the archive cleanup utility can also be used to export and delete version comments. By
default, these comments are left intact.

Version Incrementing
The FactoryTalk AssetCentre Archive uses a checksum compare to distinguish between two different files.
In order for a newly checked-in file to receive an incremented version number, it must return a different
checksum value than the latest file already checked in to the archive.

Due to the way in which the checksum value is calculated, only changes to the file itself will alter the file
enough for FactoryTalk AssetCentre to recognize a difference. An example of a file alteration which would
not return a different checksum value would be a change to the date/time stamp of the file.

Maximum File Size

The maximum file size that can be added to the FactoryTalk AssetCentre Archive is slightly larger than two
gigabytes. File additions exceeding this size limit will be automatically cancelled in most versions of
AssetCentre, whereas the attempt was made and then failed in older versions (v2.21, v2.21.01 only.)

Manual File Check-in

Occasionally it is necessary to check in a file version that was not updated using the check in/check out
functionality of the FactoryTalk AssetCentre client. In this case, it is possible to do a check-out on the file
within the FactoryTalk AssetCentre Archive without getting a local version, then to point at the desired
version of the file to add to the file’s archive. This operation would thus allow an ‘orphaned’ file version to
be checked into the archive without having to create an entirely new file. See Answer ID 50986 - How do I
manually check in a file to the FactoryTalk AssetCentre archive.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 37 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Force Comments on Check-in

A FactoryTalk AssetCentre system administrator can force users to enter comments on the work completed
before check-in of the file to the archive. The “Allow Empty Comment at Check-in” feature security policy
is set to allow by default for both “FactoryTalk Administrators” group and “All Users”, and is global,
meaning that it will apply to all archived assets. Removing a group or user from the policy setting results in
an implicit denial, meaning the user would be required to enter comments. See Answer ID 620774 -
FactoryTalk AssetCentre Archive Frequently Asked Questions.

Archive Historical Reporting

It may be desirable to perform historical reporting on a FactoryTalk AssetCentre archive, outside of the
capabilities present in the FactoryTalk AssetCentre client. While the client offers information on all
archived files, it is possible to perform broader analysis of the archive contents using SQL Server, including
historical archive activity and archive asset types. A SQL Server script provided by Rockwell Automation
can be used to install a SQL Server view into the AssetCentre database on the system’s SQL Server, which
can be used to query and potentially export information on the entire archive’s contents.

For more information on and to download the SQL Server script see Answer ID 58297 - Historical Reporting
on a FactoryTalk AssetCentre Archive.

Archive Binders
A binder is a collection of files and folders that is treated as a single unit. For example, when a binder is
checked out, all of the contents are checked out and placed in the working folder. Binders are used as the
master files for remote computer assets, and do not count against the licensed asset capacity.

Archive to Archive Compare

As of v4.10, the FactoryTalk AssetCentre client can be used to compare different files or versions of the
same file from within the archive itself, without requiring a check-out. This feature will also allow for a
comparison of files that are not part of the archive (e.g., compare the latest version in archive to a different
file on the user’s desktop.) For assets that already have compare engines defined, such as RSLogix5000
ACD files, the compare will occur without further configuration. For other files, like TXT documents, a
user-configurable compare utility can be defined. A compare engine can be configured for use with Generic
FTP Disaster Recovery tasks or Archive to Archive comparisons, but not both simultaneously.

Archive to Archive Compare Clean-up

Compare Engines will extract any required files from the archive and store them locally to run the compare.
Once the compare is complete, these files will remain on the local hard drive to help speed future compares.
To remove these files, use Tools -> Options -> Compare Configuration -> Erase All.

RSLogix 5000 / Studio 5000 Logix Designer Linking Files

When a *.ACD file is acquired from the FactoryTalk AssetCentre archive, an accompanying *.ASC file is
created in the same directory. This file is used by the design editor to link the original *.ACD file into the
AssetCentre archive. In systems with very large asset trees, this may cause a delay when opening the file in
the design editor. This delay can be eliminated using the Files -> Options -> Archive Options checkbox to
restrict the *.ASC file creation.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 38 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

RSLogix 5000 / Studio 5000 Logix Designer Backup Files

A single *.ACD file is used to manage Logix 5000 assets. By default, the RSLogix 5000 and Studio 5000
Logix Designer editors automatically create up to 3 backup files from the original *.ACD as operators make
edits. When the original *.ACD file is checked back into the FactoryTalk AssetCentre archive, these backup
files will not be automatically removed by AssetCentre. It is recommended that this setting be disabled
within the Logix editors from Tools -> Options -> Application.

Archive Extractor
The FactoryTalk AssetCentre Archive Extractor is available to system administrators for the purposes of
archive high availability. In the event of AssetCentre Server downtime, the Archive Extractor can be used to
retrieve files from archive, allowing users access to configuration files at all times. For more information on
the Archive Extractor, refer to Answer ID 62622 – FactoryTalk AssetCentre Archive Extractor.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 39 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre Disaster Recovery Capability

The FactoryTalk AssetCentre Disaster Recovery capability allows users to configure the FactoryTalk
AssetCentre system to upload the program files from their assets at scheduled intervals. These files can then
be checked into the FactoryTalk AssetCentre Archive, and/or compared to a last known good version to
generate a difference report.

Disaster Recovery is currently available the following capability options:

• Disaster Recovery for Rockwell Automation
• Disaster Recovery for Fanuc robots
• Disaster Recovery for Motoman robots
• Disaster Recovery for ABB robots
• Disaster Recovery for Remote Computers
• Disaster Recovery for Siemens S5
• Disaster Recovery for Siemens S7
• Disaster Recovery for Remote FTP
• Disaster Recovery for Custom Devices
• Disaster Recovery for Asset Inventory

Refer to Answer ID 718699 – FactoryTalk AssetCentre Disaster Recovery Device Support.

Agent Software
FactoryTalk AssetCentre makes use of the FactoryTalk AssetCentre agent to perform scheduled Disaster
Recovery tasks. Each agent utilizes different Rockwell Automation software programming packages to
perform the Disaster Recovery upload operations:

• RSLogix 5000 / Studio 5000 is required to support ControlLogix and CompactLogix

processors.
• RSLogix 5 is required to support PLC-5 processors.
• RSLogix 500 is required to support SLC-500 and MicroLogix processors.
• Drive Executive or Drive Executive Lite (v5.01 or later) is required to support Rockwell
Automation Drives. RSLogix 5000 cannot be used for Rockwell Automation Drive Disaster
Recovery.
• FactoryTalk View Studio required to support PanelView Plus.

In addition to these programming packages, two different communication software packages are used:

• RSLinx Classic required to support all processors and drives

• FactoryTalk Linx required to support PanelView Plus

None of the software packages installed on the agent computer require activation for use with Disaster
Recovery, with the exception of the full version of Drive Executive (no licenses are required for the lite
version of Drive Executive). While these products won’t operate with full functionality without activations,
FactoryTalk AssetCentre Disaster Recovery will be able to use them.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 40 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Task Execution
Each schedule is comprised of one or more tasks, where a task is the action to be performed on a specific
asset (e.g., backing up a PanelView Plus.) During a schedule’s execution, each task is assigned one at a time
to the next available agent. A single agent host is capable of servicing multiple tasks simultaneously, as long
as the asset types are different (assets being generally grouped by the capability licensing.)

For example, a Remote Computer task and a ControlLogix task could execute simultaneously, but a
ControlLogix task and SLC task cannot.

VerificationAgent Service
The VerificationAgent service is responsible for Disaster Recovery operations of all Rockwell Automation
controllers, legacy drives, PanelView, and PanelView Plus. The VerificationAgent requires an account (i.e.
AssetCentre_DR) with the proper permissions, which enables the VerificationAgent service to work with
Logix secured controllers v20 and above. Consequently, the VerificationAgent service does not support the
Local System logon. For more information, refer to Answer ID - FactoryTalk AssetCentre Disaster
Recovery Troubleshooting with RSLogix 5000 v20 and greater.

Agent Architecture and Configuration – v5.0 and earlier

All FactoryTalk AssetCentre agents participating in a v5.0 or earlier system must be configured equally.
This means that all agents must have the same software installed – including the same versions – and be able
to communicate with all assets in the system.
The FactoryTalk AssetCentre server will assign schedules to any available agent regardless of how it may be
configured. Thus, all agents must be configured the same such that they appear equal in the eyes of the
server.

Agent Architecture and Configuration – v6.0 and later

Prior to v6.0, all agents had to be created equally, as the AssetCentre server treated all agents the same. As
of version 6.0, Agent Grouping allows for the creation of specialized agents, removing the requirement for
identically configured agents. An agent now need only be configured for use with the specific assets
configured with the agent group(s) to which it is a member. For example, if an agent belongs to the
ControlLogix agent group, but not the PLC5 agent group, it would need to have the Logix 5000 software
installed but not Logix 500.

Determining Necessary Number of Agents

A FactoryTalk AssetCentre agent is capable of servicing approximately 100 assets every 12 hours. This
approximation is based on Rockwell Automation testing of various types of devices, network loads, and
program file sizes, and should be used for estimation purposes. Each asset type results in a different average,
which is further variable when project sizes and network types are taken into account. For more detailed
information on granular estimation, see Answer ID 106118 - Determining the Necessary Number of
FactoryTalk AssetCentre Agents.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 41 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Creating Disaster Recovery Schedules

When creating a Disaster Recovery schedule, it is recommended to create the schedule at a container level
rather than a device specific level. Grouping assets with similar needs (e.g., assets that need to be backed up
on the same timeline) into the same container will allow a single schedule to be created that will apply to all
assets within the container. Not only will this increase efficiency in initial schedule creation, but any
subsequent changes to the container (e.g., asset removal, asset insertion) will automatically propagate to the
schedule without user intervention.

Note that when a start time for a schedule is originally specified, that start time is based on a 24 hour clock.
This means that if the start time has already passed for the day on which the schedule is created, the next run
will be scheduled for the following day (as opposed to immediately running).

Archive Check-In with Disaster Recovery

Disaster Recovery provides two different basic operations that can affect the archive: Backup and Backup
& Compare. By default, the Backup operation will upload the asset’s configuration file and check it into
the FactoryTalk AssetCentre Archive without doing any comparisons, regardless of whether or not the file is
different from the latest version already checked into the FactoryTalk AssetCentre Archive.

In contrast, the Backup & Compare will upload the asset’s configuration file and compare it to a designated
version already checked in to the archive, but by default, will not check the uploaded file into the archive.
To use this function to also check the file into the FactoryTalk AssetCentre Archive, the Promote New
Upload to Master property of the device within the schedule must be set to true. This will cause the
uploaded file to be checked into the FactoryTalk AssetCentre Archive when differences are found between it
and the latest version already checked in, and will automatically promote the uploaded version as the master
version of the file.

Supported Controller ControlLogix Firmware Versions

With regard to the Disaster Recovery for Rockwell Automation capability, it should be noted that
ControlLogix controllers at firmware version 12 and higher are acceptable. Any versions prior to version 12
are not fully supported. SLCs and PLC-5s are supported regardless of series/revision.

Support for Studio 5000

Studio 5000 Logix Designer is supported with FactoryTalk AssetCentre v4.0 and later. It should be noted
that Studio 5000 and Logix 5000 support different operating systems, which can make selecting a single
agent or client operating system complicated. Using Agent Groups can allow a wide variety of Logix
versions to be supported since a single operating system need not be selected. Refer to the Product
Compatibility and Download Center for operating system support across various software products.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 42 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Disaster Recovery through a ControlLogix Gateway

A ControlLogix Gateway is defined as a ControlLogix chassis with more than one communication module.
The FactoryTalk AssetCentre agent would communicate with one module, then across the ControlLogix
backplane, using the second module to access a different network of assets.

In general, because FactoryTalk AssetCentre agents use RSLinx Classic or FactoryTalk Linx, depending
upon the asset) to communicate with assets, if the appropriate Linx application can browse to the asset, then
AssetCentre will be capable of performing Disaster Recovery tasks upon it.

Note: ControlLogix Gateway communications add complexity to both Linx and the ControlLogix
chassis itself. It is recommended that this configuration be used sparingly.

Disaster Recovery on ControlLogix Assets

ControlLogix assets present a wide variety of ways in which a project can be created. Generally, it is to
design a ControlLogix project with proper programming procedures as detailed in the ControlLogix Design
Considerations (e.g., use arrayed tags instead of scattered tags.) FactoryTalk AssetCentre Disaster Recovery
performance differences between arrayed and non-arrayed projects, especially in larger program sizes,
ranges from noticeable to extreme. For more detailed information, see Answer ID 106118 - Determining the
Necessary Number of FactoryTalk AssetCentre Agents.

Disaster Recovery with ControlLogix Source Protection

Source Protection is supported with Disaster Recovery. If the source key is configured within the ACD file,
the Logix Designer Compare Utility will compare the source protected contents. The source key path must
be configured in the ACD file when logged in as the user configured to run the VerificationAgent service,
and the key file must be available on each AssetCentre Agent. For more information, refer to Answer ID
1070640 – FactoryTalk AssetCentre Disaster Recovery with Logix Designer Source Protection.

ControlLogix Change Detect

As of v4.10, FactoryTalk AssetCentre can monitor a v20 or higher ControlLogix asset for any changes in
real-time. If a change is detected, AssetCentre will monitor for any additional changes for a user specified
amount of time, then generate a report including all changes during this period. If changes are still occurring
after the period has timed out, AssetCentre will continue monitoring by starting a new period.

Change detect is made possible by FactoryTalk AssetCentre monitoring the controller’s change log. While
not as detailed as Disaster Recovery compare report, this feature is intended to provide real-time feedback on
the controller’s status. The change log is a circular store inside the controller capable of up to 100 entries. In
the event of changes to the controller during a disconnect, AssetCentre will immediately detect the changes
upon restoration of communications, and log all changes during the disconnect period.

As a general recommendation, no more than 500 ControlLogix assets should be configured for use with the
Change Detect feature, with a 1:100 maximum ratio of agents to Change Detect assets.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 43 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

ControlLogix Change Detect Scheduled Task Creation

As of v4.10, the Change Detect scheduled task is available in FactoryTalk AssetCentre. Creating this
schedule will automatically add any available v20 or higher ControlLogix asset from the point of creation in
the asset tree. There is no time property for this task; once enabled, it will run all of the time. Due to this,
there is no resource-driven reason to break apart the asset tree into separate Change Detect scheduled tasks
(i.e., it is recommended to create the Change Detect schedule at the root AssetCentre node of the asset tree.)

Note: Backup and Backup & Compare operations will run normally while the Change Detect
scheduled task is running. Monitoring the same device that is being backed up is fully supported.

ControlLogix Change Detect Capable Assets

As of v4.10, RSLogix5000 assets have the Change Detect Capable property. This property will determine
whether an RSLogix5000 device can be added to a Change Detect scheduled task. The property is read-only,
and is automatically set when the device path is set. For any existing assets, or assets that have been
upgraded, this property will not automatically update; a new browse is required.

ControlLogix Change Detect with L6x Controllers

On L6x Change Detect assets, use RSLogix 5000 / Studio 5000 to configure the ControlLogix audit value
with the “Correlation affected” option disabled. Leaving this option enabled could lead to unexpected
behavior with the Change Detect schedule, including a repeating loop of Non-Consecutive Log Sequence.
See Answer ID 482097 - FactoryTalk AssetCentre: Non-Consecutive Log Sequence during Change Detect
Schedule for more details.

PanelView Plus Disaster Recovery with Multiple Agents

When using multiple FactoryTalk AssetCentre agents in a system with Disaster Recovery configured for
PanelView Plus assets, specific configuration may be necessary. In versions previous to 5.30, when
FactoryTalk Linx discovers a new device, it is added to the FactoryTalk Linx tree and given a unique name
for that installation of FactoryTalk Linx. These unique names are assigned to similar devices based on the
order in which they were browsed. This can cause confusion between two different instances of FactoryTalk
Linx, as there is no defined order in which new devices shall be named.

As of versions 4.0 of FactoryTalk AssetCentre, 6.0 of FactoryTalk View ME, and 5.30 of FactoryTalk Linx,
assets were updated to use the IP address of a device instead of its FactoryTalk Linx generated name. If
using this combination of versions or higher, ensure that PanelView Plus assets have statically assigned IP
addresses, or dynamic reservations; the IP address in the asset will not update if the device’s address
changes. If using versions previous to these, see Answer ID 63906 - Configuring FactoryTalk AssetCentre
for use with multiple RSLinx Enterprise installations for information on how to manually assign device
names in FactoryTalk Linx, thus ensuring proper asset linking.

Disaster Recovery with Rockwell Automation Drives

In versions prior to v6.0 of FactoryTalk AssetCentre, only drives administered by the Drive Executive /
Drive Tool software were supported. As of v6.0, drives that are administered by Unified Device
Configuration (UDC, embedded within the CCW programming suite) are also supported. The RA Drive
asset corresponds to drives that are configured using the Drive Executive / Drive tools software. The RA
Motor Control asset corresponds to drives that are configured using UDC within CCW.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 44 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Rockwell Automation Drives Database Updates

Disaster Recovery operations can be affected by the availability of Rockwell Automation drives profiles,
even if the drive itself is not a configured asset. If a program such as Studio 5000 is unable to open an
asset’s configuration file due to a drive definition, the Disaster Recovery schedule will fail. Ensure that the
drives database is up to date on all FactoryTalk AssetCentre agents.

Generic FTP Device Compatibility

When performing backups or backup and compares on Generic FTP devices containing subdirectories, the
FTP device must support both the “DIR” and “ls” commands. Identical directory listings should be
displayed for each command, though the format will differ.

Note: If no user account is specified, the anonymous account will be used for FTP access. Refer to Answer
ID 591465 - What user account does the Generic FTP Device use when there is no password set.

Generic FTP Custom Comparisons

As of version 8.0 of FactoryTalk AssetCentre, Compare Engines can be configured for use with Generic FTP
Disaster Recovery tasks. When a Compare Engine is configured for use with Generic FTP Disaster
Recovery tasks, it can be selected in the file configuration of the task (as opposed to the default Checksum
option). A Compare Engine can be used for Generic FTP Disaster Recovery tasks or Archive to Archive
comparisons, but not both simultaneously. It is recommended that the report output folder be utilized only
be the compare engine so an independent process does not interfere with the report collection. For more
information, refer to Answer ID 1071802 – FactoryTalk AssetCentre Compare Engines.

Disaster Recovery with Stratix Switches

As of version 9.00 of FactoryTalk AssetCentre, 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 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. The Stratix Switch assets are scheduled as part of Disaster Recovery
for Rockwell Automation tasks.

FactoryTalk AssetCentre only supports Stratix Switches with password authentication method enabled. User
account with administrative privileges (Privilege Mode – Enable Password) is required for Disaster Recovery
operations of a Stratix Switch asset. A global maximum time duration can be set for the data transfer request
between the Stratix Switch and FactoryTalk AssetCentre. This setting can be configured under Tools

Options
Stratix Switch from within the FactoryTalk AssetCentre client.

Note: FactoryTalk AssetCentre will not backup the vlan.dat file if renamed. If an additional file is
created to store vlan information, only vlan.dat will be backed up by the Disaster Recovery operation.

Stratix switches are not natively supported assets within FactoryTalk AssetCentre, but it is possible to
include them as part of a Disaster Recovery schedule by making use of their FTP server functionality. Refer
to Answer ID 595646 – Stratix Disaster Recovery with FactoryTalk AssetCentre for detailed information.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 45 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Disaster Recovery on Remote Computers

Disaster Recovery for Remote Computers provides the ability for FactoryTalk AssetCentre to back up and
verify the contents of a shared network folder on a computer in the system. This capability makes use of the
Remote Computer asset, which counts against the licensed asset capacity. The contents of the shared folder
are stored in the FactoryTalk AssetCentre archive as a binder.

The FactoryTalk AssetCentre agent accesses the remote computer using a UNC path, which points to a
shared folder on the remote computer. Along with the UNC path, a username and password is entered as
part of the asset configuration. This user will need read access to the shared folder; write access is not
required. For more information on UNC paths with the Remote Computer asset, see Answer ID 66337 -
Remote Computer asset configuration for FactoryTalk AssetCentre Disaster Recovery.

Using Disaster Recovery for Remote Computers on Locked Files

Files that are locked and/or in use when a Remote Computer schedule is run cannot be backed up by the
FactoryTalk AssetCentre agent. For instance, a FactoryTalk View SE server that is currently being used in
product will have its files locked, meaning that the FactoryTalk AssetCentre agent cannot back up a running
View SE HMI server. For more information, see Answer ID 70252 - Backing up Locked Files with
FactoryTalk AssetCentre.

Disaster Recovery with FactoryTalk View Site Edition

As of version 9.00 of FactoryTalk AssetCentre, a FactoryTalk View SE asset is now available for Disaster
Recovery operations. The FactoryTalk View SE asset is capable of backing up the entire FactoryTalk View
SE network application (APB file) including the HMI server, FactoryTalk Directory, FactoryTalk Linx, and
FactoryTalk Alarms & Events. It is possible to export the HMI server content from within the Archive plug-
in without the need of checking-out the entire application. A FactoryTalk View SE compare operation type
returns a checksum report. The FactoryTalk View SE assets are scheduled as part of Disaster Recovery for
Rockwell Automation tasks.

FactoryTalk AssetCentre supports Disaster Recovery operations for FactoryTalk View SE version 11.00 and
higher. FactoryTalk View Studio Enterprise software must be installed on the agent computer assigned to
perform Disaster Recovery operations.

The backup process has been fully integrated into FactoryTalk AssetCentre. Therefore, no configuration is
required for the backup process on the FactoryTalk View SE system. FactoryTalk AssetCentre supports
both, a FactoryTalk user and Windows user (domain or local) when configuring the FactoryTalk View SE
asset.

In a redundant FactoryTalk View SE system, no additional configuration is necessary when configuring the
FactoryTalk View SE asset as FactoryTalk AssetCentre will back up the active HMI server. Note that if the
FactoryTalk Directory Server is unavailable, FactoryTalk AssetCentre will not be able to back up the
FactoryTalk View SE network application. In general, it is recommended that the FactoryTalk Directory
Server be deployed on a separate host. See Answer ID 58803 - Network FactoryTalk Directory Best
Practices for more information on setting up a FactoryTalk Directory.

Note: Disaster Recovery schedules for FactoryTalk View SE asset and FactoryTalk Directory asset
cannot be run at the same time on an agent computer.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 46 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

As of version 8.0 of FactoryTalk AssetCentre, there is no native asset representing a FactoryTalk View SE
HMI server, it is possible to make use of Disaster Recovery for Remote Computers to back up an HMI
server. Using a Windows Scheduled Task and the FactoryTalk View SE Backup/Restore utility, the HMI
server can be checked into archive and/or compared as part of a Disaster Recovery schedule. For more
information, see Answer ID 475421 - FactoryTalk AssetCentre: Back up FactoryTalk View SE HMI Server.

As of version 6.0 of FactoryTalk AssetCentre, it is also possible to create a Custom Device to service a
FactoryTalk View SE HMI server. See Answer ID 634595 – Building Custom Devices for use with
FactoryTalk AssetCentre Disaster Recovery for more information on how to do so.

Note: Creating Custom Device assets to service FactoryTalk View SE HMI servers should be used
only in conjunction with Agent Groups. It is not recommended to install a multi-purpose Agent on
an HMI server due to system resource utilization.

Finally, as of version 10.0 of FactoryTalk View SE, the File Viewer Utility can be used to compare
differences in RecipePro+ files of FactoryTalk View SE applications. A Custom Device Disaster Recovery
task can be used to convert the RecipePro+ files to CSV format, with a Custom Device Compare on the plain
text. Refer to Answer ID 1071414 - Automatically Compare FactoryTalk View SE RecipePro+ Changes
Using FactoryTalk AssetCentre for more information.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 47 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Disaster Recovery with the FactoryTalk Directory

As of version 8.00 of FactoryTalk AssetCentre, a FactoryTalk Directory asset is available for Disaster
Recovery operations. The FactoryTalk Directory asset uses FactoryTalk Security credentials to log into the
directory, and is capable of backing up specific applications (hierarchy only) or the entire directory,
including security configurations. FactoryTalk Directory assets are scheduled as part of Disaster Recovery
for Rockwell Automation tasks.

Note: A FactoryTalk Directory backup will always return differences. Version control should be
monitored to prevent a large number of versions.

Custom Device Configuration with Scripted Mouse Movements

As of version 6.10 of FactoryTalk AssetCentre, scripting mouse movements can be accomplished with
Custom Device Plug-in using the agent application mode. In version 6.0, this behavior is only supported on
Windows Server 2003 R2 SP2 and Windows XP SP3 operating systems. Because the custom device
configuration will execute on the FactoryTalk AssetCentre Agent as a service, operating systems later than
Windows Server 2003 are unable to support this behavior. Refer to Answer ID 639670 – FactoryTalk
AssetCentre Custom Device Plug-in with Scripted Mouse Movements for more information.

As part of expanding third-party support, an integration solution with an open source scripting tool called
AutoIt is available as a sample solution for Disaster Recovery operations using a Rockwell Automation
ControlLogix controller. The AutoIt integration solution includes sample scripts that shows the
configuration of backup and compare operations of a Logix 5000 controller. The AutoIt sample script
includes the configuration of events that can be added into the FactoryTalk AssetCentre Event Logs to reflect
operation statuses and results. This solution utilizes the FactoryTalk AssetCentre Custom Device Plug-in
capability add-on, AutoIt scripting tool, Logix Designer Compare Tool, and Studio 5000 Logix Designer.
The AutoIt scripting tool is free to download at https://www.autoitscript.com/site/autoit/downloads/.

The AutoIt integration sample solution is intended as a guideline for anyone that needs to develop their own
scripts to perform Disaster Recovery operations with third-party devices. For more information on the
AutoIt integration, refer to Answer ID 1085184 – Building Custom Devices for third-party use with Disaster
Recovery.

Asset Inventory Management Disaster Recovery Schedules

Disaster Recovery for Asset Inventory allows the user to schedule FactoryTalk AssetCentre to browse the
network for CIP, SNMP, and/or WMI assets. These assets are collected into an *.RAAI file, which is stored
in the AssetCentre archive. The *.RAAI file can be viewed within the AssetCentre client, and can be used to
add/update the AssetCentre asset tree.

Because the network scan can take much more time than backing up an individual asset, it is recommended
that each Asset Inventory asset be configured in an independent Disaster Recovery schedule.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 48 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Asset Inventory Management with CIP Devices

Asset Inventory CIP scanning uses an RSLinx Classic driver, meaning that only Rockwell Automation assets
will be returned as part of the CIP scan (e.g., no Siemens devices would be discovered). The timeouts
associated with CIP scanning in the advanced properties of the asset correspond to how long AssetCentre
will wait for an initial CIP response, then how long to wait for a response for the CIP information. It is
recommended that these timeouts be left at the default values.

Asset Inventory Management with PanelView Plus and MobileView assets

Due to the nature of the CIP scan used to identify PanelView Plus and MobileView assets, the device address
must be manually when added to the asset tree. All of the device’s CIP properties will be transferred to the
new asset, but a FactoryTalk Linx browse out to the asset will be required to create the path. Once this is
completed, the asset can be updated using the Asset Inventory as with any other asset type.

Asset Inventory Management with SNMP Devices

Asset Inventory SNMP scanning will browse the identified address range, ping each individual address to
determine if it is available, and then send an SNMP get-request. If the device responds, the AssetCentre
service will request all available SNMP information. Note that the community string can only be set
globally, not on a per-device level.

The Asset Inventory scan uses SNMP version 2.0. Some properties can be returned from devices using v1.0
of SNMP, but v3.0 is not supported.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 49 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Product Lifecycle Management with Asset Inventory

As of version 9.00 of FactoryTalk AssetCentre, 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. Controller IO is configured under the asset properties where the user can enter the IO
manually or automatically read the IO of the archived controller file. The controller IO lifecycle information
can be viewed from the Asset Lifecycle plug-in under the Assets view. Assets supporting this feature
includes Logix 5000 controllers, SLC 500 processors, MicroLogix processors, and PLC-5 processors.
Controller IO lifecycle information is part of Disaster Recovery for Asset Inventory. For more information,
refer to Answer ID 1071178 – FactoryTalk AssetCentre Assets Lifecycle.

Note: When configuring the asset controller IO, the automatic option only applies to Logix 5000
controllers (ACD file).

In version 8.00 and higher of FactoryTalk AssetCentre, asset lifecycle information can automatically be
synchronized from the Product Compatibility and Download Center (PCDC). This functionality requires the
FactoryTalk AssetCentre server to have a connection to the internet, which is used to query the PCDC for
asset catalog information. For estimation purposes, it will take approximately one minute per one thousand
unique catalog queries. For more information, including server communication requirements, refer to
Answer ID 1071178 – FactoryTalk AssetCentre Assets Lifecycle.

In versions 7.10 and higher of FactoryTalk AssetCentre, users can use the “Export for PCDC” option,
allowing the Asset Inventory CIP scan results to be exported as an RAAI file, and imported into the Product
Compatibility and Download Center website (PCDC). The PCDC view will show product compatibility,
firmware downloads, and lifecycle status of the scan results. The “Export for PCDC” option is available by
selecting the RAAI file under the asset tree and performing a right click, or by selecting the RAAI file and
opening the archive plug-in. Note that a Rockwell Automation account is required for import in to the
PCDC website.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 50 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre Calibration Management Capability

The Calibration Management Capability leverages ProCalV5 to allow users to manage the process of
calibrating their process devices from within the FactoryTalk AssetCentre client. This should not be
confused with Process Device Configuration, as Calibration Management manages the process of
calibration, it does not provide any tools for calibrating or interacting with the instruments directly.

Building a Process Device Asset Hierarchy

There are five FactoryTalk AssetCentre assets that can be used and linked directly with ProCalV5: System,
Equipment, Loop, Instrument, and Test Instrument. For the purposes of configuring a hierarchy:

o Systems can contain any combination of Equipment, Loop, Instrument, and Test Instrument assets,
along with other system assets.
o Equipment assets can contain any combination of Loop, Instrument, and Test Instrument assets. This
is the only asset for which calibration data cannot be defined, however reports may be run on it.
o Loops can contain Instrument and/or Test Instrument assets.
o Instruments and Test Instruments are strictly child assets.

A parent asset cannot be added to a child asset, e.g., a Loop asset cannot be added to an Instrument asset as
part of the asset tree hierarchy. Note that defining the asset tree’s hierarchy will not inherently add a child
asset to a parent asset (e.g., an Instrument to a Loop) within ProCalV5; the asset tree hierarchy is merely a
logical structure. For a complete understanding of each asset, see Answer ID 63227 - FactoryTalk
AssetCentre Calibration Management FAQs.

Process Device Naming

It is important to understand the relationship between the process device asset created in the FactoryTalk
AssetCentre asset tree, and the ProCalV5 device to which it is linked. The FactoryTalk AssetCentre asset
tree and the process device assets within it can be considered a hierarchical view of a Process and
Instrumentation Diagram (P&ID) of a plant. In this sense, the process device assets act as logical
placeholders for the various instruments that compose the process system, which can then be linked to an
actual device.

The actual devices are stored in the ProCalV5 database, which holds a Master Instrument Record (MIR) for
each individual device. While the FactoryTalk AssetCentre asset tree placeholders will indicate an
instrument’s location, the instrument itself may not necessarily be static. For instance, if a pressure sensor at
P&ID number PT100 fails, it will need to be replaced. The P&ID number will not change, but the device
itself will. In FactoryTalk AssetCentre, the PT100 process device asset will only be unlinked from the
original, faulty device’s record in ProCalV5, and re-linked to the new device’s record.

P&ID numbers can also be tracked in ProCalV5 to assist in categorizing the various devices. While the
device name itself should be unique to the device (and not the P&ID number), the Additional Info tab offers
multiple fields (P&ID Number, P&ID revision) to help keep track of where a particular device belongs in a
given system.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 51 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

ProCalV5 Component Architecture Considerations

There are two ProCalV5 components required for FactoryTalk AssetCentre Calibration Management: the
ProCalV5 Server and the ProCalV5 Client. The ProCalV5 Server component must be installed on the same
computer as the Microsoft SQL Server hosting the ProCalV5 database. The ProCalV5 Client must be
installed on each FactoryTalk AssetCentre Client computer from which Calibration Management access is
desired. It is not possible to use the ProCalV5 client independently, nor to locate the ProCalV5 server apart
from the Microsoft SQL Server hosting its database.

Asset Links
Assets to be used with the Calibration Management capability are created in both FactoryTalk AssetCentre
and ProCalV5. The asset created in FactoryTalk AssetCentre is then linked to an asset created in ProCalV5.
At this point, the calibration management functionality is performed in ProCalV5 on the ProCalV5 asset,
with information available through the linked asset in the FactoryTalk AssetCentre client.

Calibration Management Windows Security Settings

By design, closing ProCalV5 will cause the software to attempt to make Windows registry edits. If the user
logged into Windows does not have adequate privileges to edit the specific registry key, this will cause
ProCalV5 to fail in its attempt to edit the registry, thereby disallowing it from closing. While this does not
cause any further problems, the user will have to end the ProCalV5 process in order to close it.

Allowing write privileges to the ‘HKEY_LOCAL_MACHINE\SOFTWARE\ProCal V5’ key will resolve

this problem. Registry editing privileges can be extended to a user or group of users for this specific key
without opening the entire registry (or Operating System) to the user(s). See Answer ID 60059 -
FactoryTalk AssetCentre Calibration Management User Configuration for more information on how to
accomplish this.

Note: The necessary security privileges extend only to the Windows user; FactoryTalk Security
privileges do not have any bearing in this context.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 52 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk AssetCentre Process Device Configuration Capability

The Process Device Configuration capability provides the ability to manage process device configuration
directly from within the FactoryTalk AssetCentre client by leveraging FTD/DTM technology. Users are now
able to load multiple DTMs, utilizing an FDT frame from within the FactoryTalk AssetCentre client itself.

FDT/DTM Technology
The Field Device Tool (FDT) Group created FDT technology to standardize the communication interface
between field devices and systems. FDT is independent of the communication protocol and the software
environment of either the device or host system. This standardization allows device manufacturers to
provide a common way to access their devices in the form of Device Type Managers (DTMs.)

DTMs provide a unified structure for accessing device parameters, configuring and operating the devices,
and diagnosing problems. DTMs can range from a simple Graphical User Interface (GUI) for setting device
parameters to a highly sophisticated application capable of performing complex real-time calculations for
diagnosis and maintenance purposes.

It is important to note that FactoryTalk AssetCentre Process Device Configuration provides an FDT window
in the form of the FactoryTalk AssetCentre client. Any DTM can then be loaded into this window, but
FactoryTalk AssetCentre itself does not provide DTMs. These DTMs are written and provided by device
manufacturers, such as Endress & Hauser.

For more information on FDT/DTM technology, visit the FDT Group’s website: http://www.fdtgroup.org/en

System DTM Management

Rockwell Automation recommends that only the DTMs in use for a given system be installed. For example,
if a manufacturer’s DTM Library includes 1000 DTMs, the user should perform a custom installation and
select only those DTMs that will be in use, not installing the rest of the library that would go unused.

There is no maximum limit regarding the total number of DTMs that can be installed in a FactoryTalk
AssetCentre system, but known issues can occur if too many DTM entries are added to the DTM catalog.
These issues include the Catalog Scan hanging, and the Catalog not opening properly.

In an effort to avoid these issues, the recommended limit of DTMs to be installed on a single client is 1,000.
Again, this is not an enforced maximum, and this recommendation will not apply to all DTM libraries.
Because each DTM will be different in size, this number is a conservative recommendation to limit risk
during the catalog scan.

Similarly, the maximum number of DTMs recommended for installation in an entire FactoryTalk
AssetCentre system (i.e., the total number of DTMs installed on all clients) is 10,000. This recommendation
is intended to limit the risk of the total DTM catalog size becoming too large for the client cache to manage.

For more information, refer to Answer ID 1048639 – Planning DTM Installation with FactoryTalk
AssetCentre.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 53 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Client DTM Management

It should be understood that, while the DTM catalog is stored by the FactoryTalk AssetCentre server and
propagated out to each FactoryTalk AssetCentre client, the individual DTM files are installed and located on
each physical FactoryTalk AssetCentre client PC. This means that if a DTM is installed on a FactoryTalk
AssetCentre client and then scanned into the DTM catalog, the same DTM must be installed on every other
FactoryTalk AssetCentre client PC that will be using it.

Similarly, all DTM upgrades should be performed at once to ensure that all DTM versions across the
FactoryTalk AssetCentre clients are uniform. If the FactoryTalk AssetCentre client detects a version
difference between the DTM registered in FactoryTalk AssetCentre and the version installed locally, it will
attempt to modify the DTM’s link to use the locally installed version. If multiple versions exist across
multiple clients in the application, this can result in a constant looping effect, where each FactoryTalk
AssetCentre client changes the DTM upon opening.

DTM Support
FactoryTalk AssetCentre supports all instruments/devices that provide DTMs certified with the FDT Group
1.2 specification standard. For more information on how to research this availability, refer to Answer ID
620039 – DTM Support with FactoryTalk AssetCentre.

Building a DTM network

The DTM Network tree provides FactoryTalk AssetCentre with the communications path to all process
device assets within the system. Generally speaking, the DTM network is created by stacking two types of
DTMs (communication DTMs and Device DTMs) until the process device is reached. A new or empty
DTM network will only have one node: the Host PC node. This node will act as the root upon which to
build the rest of the DTM Network, and represents the computer from which the process device will be
accessed.

A DTM’s ability to be placed at different hierarchical levels within the DTM Network is determined by two
properties:

o Upstream protocol – defines how the DTM will communicate with nodes in the DTM Network at the
hierarchical level above
o Downstream protocol – defines how the DTM will communicate with nodes in the DTM Network at
the hierarchical level below

Thus, DTMs added at the first hierarchical level have no specific upstream protocol because they are simply
a bridge used by the Host PC to communicate to the next level(s) of DTMs. The downstream protocol of
these first-level DTMs is the communication path that the Host PC will use (e.g., the HART Communication
DTM’s downstream protocol is HART.) The final DTM in any branch will be the device DTM to which the
user is attempting to communicate; device DTMs do not have a downstream protocol because they are the
destination to which a DTM Network is being built.

For more information on building a DTM network, refer to Answer ID 64709 - Basics of DTM Networks in
FactoryTalk AssetCentre.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 54 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Process Device Configuration Editing Lock

FactoryTalk AssetCentre makes use of an editing lock to ensure that only one client can be editing Process
Device Configuration portions of the system at a given time, thereby removing any risk of overlapping edits.
The lock is removed when the editing client closes the editing component (e.g., DTM network or DTM
view,) or if the client remains disconnected from the server for approximately one minute.

If time synchronization between the FactoryTalk AssetCentre server and FactoryTalk AssetCentre client(s) is
not configured, it’s possible for the lock timeout to function incorrectly. Thus, it is strongly suggested to
time synch all FactoryTalk hosts. For more information on synching time, see the Time Synchronization
section later in this document, and for more information on the editing lock, see Answer ID 60589 -
FactoryTalk AssetCentre and Time Synchronization.

Note: This editing lock time out only occurs when the network connection between FactoryTalk
AssetCentre client and server is lost. If the connection is maintained, the time out will not be used.

Field Edition
New in v3.00, Process Device Configuration Field Edition allows for the management of configuration data
in process devices while disconnected from the FactoryTalk AssetCentre server. Using the embedded
Process Device Configuration requires a maintained connection to the server, whereas using Field Edition
allows the user to check out the Field Edition files and then disconnect if desired.

Note: Associating the Field Edition files with a process device asset and checking them in and out of
the FactoryTalk AssetCentre archive not only tracks changes to the DTM Network, but also to the
offline configurations of the process devices. Offline configurations of the Field Edition process
devices are not tied to the embedded Process Device Configuration offline configurations.

When configuring an asset for use with Field Edition, the DTM Addressing Info field is not used, as this
links the asset to the embedded Process Device Configuration’s DTM Network. Instead, use the
Configuration Data field to link to the Field Edition file.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 55 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Field Edition DTM Catalog

Process Device Configuration’s Field Edition client utilizes the DTM Catalog scanned by the FactoryTalk
AssetCentre client. Doing so allows Field Edition to operate disconnected from the FactoryTalk AssetCentre
server, but requires that a client be installed locally with a scanned catalog. Any catalog maintenance or
configuration must be done via the FactoryTalk AssetCentre client.

Field Edition vs Embedded PDC

In FactoryTalk AssetCentre v6.0, several enhancements were made to the Process Device Configuration
components to improve the user experience. Some of these enhancements were isolated to the Field Edition
tool because of technical limitations in the DTM Viewer embedded in the FactoryTalk AssetCentre Client.
Due to this, some DTMs may perform differently in the Field Edition tool compared to the embedded DTM
Viewer within AssetCentre. Wherever possible, it is recommended that the Field Edition tool be used with
version 6.0 and later.

Clients Share Network Paths

Each FactoryTalk AssetCentre client will share the configured DTM network paths. This is especially
relevant in terms of process device assets linked to the DTMs established in the network paths. With this in
mind, if two clients have different network paths, only one path can be linked to an individual asset. In this
scenario, the single process device will need multiple entries in the DTM network paths, and multiple assets
configured in FactoryTalk AssetCentre (one asset for each network path, using one asset activation apiece).

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 56 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

General Asset Tree Best Practices

FactoryTalk AssetCentre is a modular software product, in that its different components can be very clearly
distributed. The common tie across all capabilities (e.g., Disaster Recovery, Calibration Management,
Archive, etc.) is the Asset Tree. The Asset Tree is a hierarchical view of the different pieces within the
application, including assets themselves (e.g., ControlLogix Processor, PLC, RA Drive, Process Device), as
well as archived files.

Asset Tree Hierarchy Best Practices

It is generally recommended to group assets with similar Disaster Recovery scheduling needs into the same
containers. Doing so will allow schedule creation at the container level, which will propagate any container
level changes (e.g., asset removal, asset insertion) to the already defined schedule automatically.

In some cases, it is desirable to group the assets and their respective configuration files in different logical
areas of the asset tree. For instance, at the root of the asset tree there would exist a container for Files, and a
separate container for Controllers. The former would hold all .ACD files and the latter would hold all
ControlLogix controller assets. This configuration can ease security settings, where access to the Files
container is more open than access to the Controllers folder, which should not need to be modified by an
average user.

Asset Tree Reporting

It may be desirable to perform reporting on a FactoryTalk AssetCentre asset tree, such as examining the
properties of assets of the same type, querying the total number of a certain type of asset, etc. While the
FactoryTalk AssetCentre client offers the user access to individual assets within the asset tree, broader
queries can be accomplished using the SQL Server. See Answer ID 58299 - Reporting on a FactoryTalk
AssetCentre Asset Tree for information on an MSSQL View that will query Rockwell assets.

Asset Tree Export/Import

In version 8.0 and higher of FactoryTalk AssetCentre, 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. In the initial release of this utility, archive assets (files/folders/binders) are not available for
import/export operations.

In versions prior to 8.0, The FactoryTalk AssetCentre Asset Tree Import/Export utility is still available, but
with less functionality. The utility can be used to export part or all of the asset tree in one FactoryTalk
AssetCentre server, then import the section into an existing asset tree. The process will strip out the
properties of the exported assets (leaving the original assets unchanged), allowing for configuration once
imported to the new system.

See Answer ID 60221 - FactoryTalk AssetCentre Asset Tree Import/Export Utility to download the utility,
and for more detailed information on its usage.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 57 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

FactoryTalk Security
FactoryTalk Security authenticates user identities and authorizes user requests to access a FactoryTalk-
enabled system. These security services are fully integrated into the FactoryTalk Directory and are included
as part of the FactoryTalk Services Platform. FactoryTalk Security includes user authentication that
determines who can open, create, modify, and delete application components, and on which hosts the actions
are allowed. It is also possible to use FactoryTalk Security to add user and group security accounts, as well
as Windows-linked accounts, and set up security for actions such as tag writes, open, and delete.

• Answer ID 30980 - FactoryTalk Security - Tips and Best Practices

User-based Access to Containers

FactoryTalk Security can be used to restrict user access to different parts of the FactoryTalk AssetCentre
asset tree without restricting access to the entire application. Security may be defined on a single element
basis of the tree, and can be inherited by any subsequent pieces of the asset hierarchy.

For instance, denying ‘read’ and ‘list children’ rights to a container will result in a user being unable to see
that container, as well as anything contained within it. Similarly, denying the same rights to a single
ControlLogix asset will result in the user being unable to see it, while still being able to interact with other
elements at its hierarchical level. See Answer ID 47483 - FactoryTalk AssetCentre users can't view asset
tree in FactoryTalk AssetCentre client for more information on these security options, and how they affect
the FactoryTalk AssetCentre client.

FactoryTalk AssetCentre Agents w/Co-located Clients Using Editor Security

In FactoryTalk AssetCentre versions prior to v5.0, it is not recommended to use clients on the same
computer as agents when editor security is configured because single sign-on must be enabled for Disaster
Recovery to properly function. This means that the FactoryTalk software pieces in use on the client (e.g.,
FactoryTalk View Studio, RSLogix 5000, etc) will not prompt the user to log in prior to use, thereby limiting
the usefulness of the audit and diagnostic logs by not accurately recording the username.

In version 5.0 and later, Single Sign-on is not required when using secured editors for PLC5, SLC500, or
Logix (v17 and up) assets.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 58 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Remote Desktop Services

FactoryTalk AssetCentre supports Remote Desktop Services (formerly Terminal Services.)

Remote Desktop Services Server FactoryTalk Components

Since the Remote Desktop Services (RDS) server will be used to host RDS sessions for the remote (thin)
clients, all software that a client would need must be installed on the RDS server itself. For FactoryTalk
AssetCentre, this means installing the FactoryTalk AssetCentre client and any design software pieces that the
client would require (e.g., RSLogix 5000 for ControlLogix processors, FactoryTalk View Studio for
PanelView Plus, etc.) Any FactoryTalk AssetCentre system using RDS should ensure that the FactoryTalk
Services Platform is using the most recent patches.

In some architectures, the thin client host will have the design software installed, and a remote session is then
opened to the RDS server on which only the FactoryTalk AssetCentre client is installed. Using this
configuration, files can be checked out of the archive using the thin FactoryTalk AssetCentre client, but the
files then stay within the remote session. This means that the locally installed design software will not have
access to the files unless transferred over the network, meaning this configuration is not generally
recommended.

While it is a supported architecture, it is not recommended to co-locate the RDS server with the FactoryTalk
AssetCentre server component.

FactoryTalk Audits with Remote Desktop Services

The FactoryTalk AssetCentre server is capable of capturing audits and events from Remote Desktop Services
(RDS) client sessions where the FactoryTalk AssetCentre client is installed. Depending upon the
configuration of the FactoryTalk Network Directory, it is possible to capture the RDS client from which the
audit was generated, as well as the FactoryTalk user (Windows linked or otherwise) logged into the RDS
session. See Answer ID 59066 - FactoryTalk AssetCentre Audits with Remote Desktop Services for more
information.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 59 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Time Synchronization
The Windows Time service (W32tm.exe) uses the Network Time Protocol (NTP) to synchronize computer
clocks on the network. Time synchronization is critical for the proper operation of many Windows services,
and to ensure the security of authentication within an Active Directory environment. Configuring time
synchronization is highly recommended in a FactoryTalk AssetCentre system for reasons including the
accurate capture of audits and events, as well as proper operation of editing clients. See Answer ID 60589 -
FactoryTalk AssetCentre and Time Synchronization for more information.

• In workgroup environments, configure Windows Time to synchronize all the FactoryTalk computer
clocks to an authoritative time server (e.g., the FactoryTalk Directory).
• In domain environments, Windows Time should be automatically configured on each computer
(when they join the domain) for the appropriate authoritative time server (i.e., the domain controller
that is also the PDC emulator).
• In either environment, the authoritative time server should then be synched to:
o a reliable time server on the Internet
o a locally-connected hardware time source such as an atomic clock
• Check the Event Viewer System log of each computer to verify that the time is being updated
properly.

System Redundancy
FactoryTalk AssetCentre does not support native server redundancy. However, due to the load balancing
system, FactoryTalk AssetCentre agent redundancy is inherent. If a FactoryTalk AssetCentre agent fails
while executing a task, the task is automatically added back into the queue by the server, then assigned to the
next available FactoryTalk AssetCentre agent.

A Microsoft SQL cluster is supported, as is MSSQL mirroring as of version 6.00 and the latest patched
version of 5.00. See Answer ID 609423 - FactoryTalk AssetCentre with Microsoft SQL Server Mirroring.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 60 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

RSMACC to FactoryTalk AssetCentre Conversions

This section explains the process for upgrading an RSMACC™ Change Management system to FactoryTalk
AssetCentre. If an RSMACC Network Health or Enterprise Online Condition Monitor (EOL) system
upgrade is desired, the local Rockwell Automation office must be contacted to facilitate. RSMACC version
1.05 or later is required to upgrade to FactoryTalk AssetCentre.

During the migration process, RSMACC will be uninstalled, the RSMACC SQL databases backed up,
FactoryTalk AssetCentre will be installed, and finally the RSMACC databases will be migrated to
FactoryTalk AssetCentre. For step by step instruction, refer to the ‘Converting an RSMACC system’ section
of the FactoryTalk AssetCentre Installation Guide. Be aware that there will be a period of time during the
migration process during which no data will be logged to either the RSMACC databases or the FactoryTalk
AssetCentre database.

RSMACC Database Migration

RSMACC uses three databases: Event and Audit, Archive (w/RSMACC Change Management), and
Diagnostics and Health (w/RSMACC Network Health). FactoryTalk AssetCentre combines these databases
into one unified database (called AssetCentre). A database migration tool is provided with the FactoryTalk
AssetCentre server software to make migration as easy as possible. Because the equivalent of the RSMACC
Network Health solution is not included in FactoryTalk AssetCentre, Diagnostics and Health information
will only be logged if RSNetWorx MD is installed on the system. Otherwise, only the information imported
from RSMACC will appear in the AssetCentre database.

When the Archive database is imported into FactoryTalk AssetCentre, the creation timestamp for imported
labels reflects the time the asset was created (rather than the time the label was added). For example, if a file
in the RSMACC system was created on 7/18/2006 1:47PM, all the imported labels will show a date and time
of 7/18/2006 1:47PM even though the labels were created some time after that. The imported Archive history
and Audit trail correctly reflect the historic label creation date.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 61 of 63
 FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS

Additional Reference Links

Tricks and Tweaks
• Answer ID 50986 – How do I Manually Check In a File to the FactoryTalk AssetCentre Archive?
• Answer ID 58297 – Historical Reporting on a FactoryTalk AssetCentre Archive
• Answer ID 58298 – Historical Reporting on FactoryTalk AssetCentre Audit and Event Logs
• Answer ID 58299 – Reporting on a FactoryTalk AssetCentre Asset Tree
• Answer ID 59541 – Backing up and Restoring FactoryTalk AssetCentre
• Answer ID 60221 – FactoryTalk AssetCentre Asset Tree Import/Export Utility

Troubleshooting
• Answer ID 43994 - Can't enter design mode in FactoryTalk AssetCentre
• Answer ID 60707 - Server Service not Starting (Client won't open)
• Answer ID 50773 - How to troubleshoot FactoryTalk AssetCentre schedule failing or doesn't
complete
• Answer ID 53693 - Waiting for Interface error when trying to run FactoryTalk AssetCentre schedule

FactoryTalk AssetCentre
• FactoryTalk AssetCentre Installation Guide
http://literature.rockwellautomation.com/idc/groups/literature/documents/in/ftac-in003_-en-e.pdf
• Answer ID 46285 - FactoryTalk AssetCentre FAQ
• Answer ID 51926 – FactoryTalk AssetCentre SQL Server 2005 Licensing
• Answer ID 56049 – FactoryTalk AssetCentre Tips and Best Practices TOC
• Answer ID 58049 – FactoryTalk AssetCentre Agent FAQ
• Answer ID 60057 – Architecting FactoryTalk AssetCentre
• Answer ID 63227 – FactoryTalk AssetCentre Calibration Management FAQs
• Answer ID 68169 – FactoryTalk AssetCentre Process Device Configuration FAQs
• Answer ID 69832 – Asset Capacity Usage in FactoryTalk AssetCentre
• Answer ID 632852 – FactoryTalk AssetCentre Agent Group FAQ
• Answer ID 634820 – FactoryTalk AssetCentre Custom Device Asset FAQ

General
• Product Compatibility and Download Center
• Answer ID 35330 - Rockwell Software Products and Antivirus Software
• Answer ID 42682 - Software Platform\Hardware Compatibility Matrix
• Answer ID 58803 – Network FactoryTalk Directory Best Practices
• Answer ID 66173 - FactoryTalk Considerations for Windows Workgroups and Domains.

FactoryTalk AssetCentre v9.00 (CPR9 SR11) Design Considerations

Rev. 2.1 Page 62 of 63
FACTORYTALK ASSETCENTRE DESIGN CONSIDERATIONS