FactoryTalk AssetCentre agent frequently asked questions

What does a FactoryTalk AssetCentre agent do?

FactoryTalk AssetCentre agents are programs that communicate with the FactoryTalk AssetCentre server and perform scheduled tasks on the server's behalf. While the FactoryTalk AssetCentre client is used to configure scheduled searches, or Disaster Recovery operations like backups, and backup and compares in the server, the agent is the piece of software that performs the scheduled operation.

For Disaster Recovery operations, the agent uses programming software (for example, Studio 5000 Logix Designer, FactoryTalk Linx, or FactoryTalk View Studio) and communications software (for example, FactoryTalk Linx) installed locally to pull files from the assets and pass them along to the server. All agents within a FactoryTalk AssetCentre system must be configured exactly the same.

Where should a FactoryTalk AssetCentre agent be installed?

FactoryTalk AssetCentre agent should be installed within the same network as the FactoryTalk AssetCentre server, client(s), FactoryTalk Directory, and SQL server. An agent can be its own independent computer, or co-located with any other FactoryTalk AssetCentre components.

It is generally not recommended to co-locate the FactoryTalk AssetCentre client with the FactoryTalk AssetCentre agent. For more details, see Knowledgebase Document ID: QA11849 - Co-locating FactoryTalk AssetCentre Client and Agent Components. Because the FactoryTalk AssetCentre agent will have system resources used at random when executing schedules, this can make using the same computer as a workstation difficult.

Can multiple FactoryTalk AssetCentre agents be installed on the same computer?

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

What is the difference between the FactoryTalk AssetCentre AgentController service and the FactoryTalk AssetCentre agent application?

The FactoryTalk AssetCentre Agent application is designed to run with the privileges of the currently logged-in session, including desktop interaction. The AgentController service runs in session 0, which runs automatically without a user being logged in. For more information on managing the agent, see Knowledgebase Document ID: QA31704- FactoryTalk AssetCentre Agent Launch Control Panel.

Can the FactoryTalk AssetCentre agent run as both a service and an application at the same time?

No. By default, the FactoryTalk AssetCentre agent is configured to run as a service. The FactoryTalk AssetCentre Agent Launch Control Panel can be used to configure the agent to run as a service or an application. For more information on managing the agent, see Knowledgebase Document ID: QA31704- FactoryTalk AssetCentre Agent Launch Control Panel.

If the Siemens connector, Mitsubishi connector, or Schneider connector is installed with the FactoryTalk AssetCentre agent, the agent will be configured to run as an application. This is necessary for Disaster Recovery to work properly for Siemens TIA Portal, Mitsubishi GX Works2, GX Works3, and Schneider Control Expert controllers.

What are the minimum system requirements for a FactoryTalk AssetCentre agent?

Generally speaking, a workstation computer will suffice (that is, a server class system is not needed). For specific system requirements, see the

FactoryTalk AssetCentre Installation Guide

.

How many FactoryTalk AssetCentre agents are needed in a system?

It depends on the size of the system and the assets within it. An agent can service approximately 100 assets every 12 hours. This number should be used for estimation purposes only, as different-sized controllers and different network bandwidths could allow for different upload speeds (for example, a PLC-5/40 on a network with no traffic will take less time to perform an upload than a full ControlLogix L64 with a heavy network load).

What does the FactoryTalk AssetCentre agent do in Disaster Recovery systems?

The agents perform the actual work of Disaster Recovery. The FactoryTalk AssetCentre server will assign a scheduled task to any available agent, which will then perform the applicable operation (for example, Backup and Compare) on the asset. Once the schedule is completed, the retrieved files and compare report are sent back to the server for storage in the archive and logs respectively.

Do FactoryTalk AssetCentre agents need to be installed in non-Disaster Recovery applications?

Yes. The agent's functions extend beyond Disaster Recovery in that they perform other scheduled operations, such as scheduled searches of the audit and event logs. Thus, at least one agent will be necessary in any FactoryTalk AssetCentre system.

Do I have to buy the software installed on the FactoryTalk AssetCentre agent?

Agents themselves are not activated. Additionally, the software that the agents make use of (for example, RSLogix 5000) does not have to be activated, except for Drive Executive. Drive Executive Lite can be used with FactoryTalk AssetCentre V2.31 (CPR9 SR1) or later agents, so that the licensed version of Drive Executive would not be needed. For more on Drive Executive Lite, see Knowledgebase Document ID: QA9623 - FactoryTalk AssetCentre with Drive Executive Lite.

In addition, when performing disaster recovery tasks for Siemens TIA Portal, Mitsubishi GX Works2 and GX Works3, and Schneider Control Expert controllers, a licensed version of the third-party editing software must be installed on the agent.

How many FactoryTalk AssetCentre agents can I have in a system?

FactoryTalk AssetCentre version 15.00 and later support both local and remote Agents. You can refer to the following for characterized system size. Exceeding these evaluated limits might impact system performance.

What is a FactoryTalk AssetCentre agent group?

Agent Groups are introduced in version 6.00 of FactoryTalk AssetCentre. For more information, see Knowledgebase Document ID: QA21618 - FactoryTalk AssetCentre Agent Group FAQ.

Are there any FactoryTalk AssetCentre agent best practices to be aware of?

For versions before 6.00, all FactoryTalk AssetCentre agents must be created equally.

All FactoryTalk AssetCentre agents participating in a version 5.00 or earlier system must be configured equally. This means that all agents must have the same software installed – including the same versions – and must be able to communicate with all assets in the system.

Version 5.00 or earlier of 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 may execute all schedules within the FactoryTalk AssetCentre system.

For more information, see Knowledgebase Document ID: QA11498 - FactoryTalk AssetCentre System Design Considerations.

Common RSLinx Classic drivers

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. When using the RSLinx Classic communications software, this path includes the RSLinx Classic driver name, meaning that the agent and client driver names must be identical.

Use arrayed tags vs. scattered tags whenever possible with ControlLogix assets

In general, it is advantageous to design a ControlLogix project with proper programming procedures as detailed in the ControlLogix Design Considerations (for example, use arrayed tags instead of scattered tags.) The performance differences between arrayed and non-arrayed projects, especially in larger program sizes, range from noticeable to extreme.