Architecting FactoryTalk AssetCentre
The topics below introduce the implementations of FactoryTalk AssetCentre version 4.10 or later.
Will time synchronization be used?
- Time synchronization is recommended, but not required for FactoryTalk AssetCentre. By default, computers that are members of a domain will synchronize time with their domain controller.
How many assets will FactoryTalk AssetCentre be servicing, if using disaster recovery?
- Assets include any controllers (PLCs, SLCs, CLXs, and so on), PanelView Plus family terminals, drives, robots, remote computers, FTP devices, or custom devices that will be configured as part of a Backup, Backup and Compare, or Change Detect operation.
- Asset count does not include files to be checked into the FactoryTalk AssetCentre Archive.
How many agents will be installed?
- All FactoryTalk AssetCentre systems require at least one agent, whether they're using Disaster Recovery. Agents are used to perform all scheduled activities, including scheduled searches.
- If using Disaster Recovery, agent count is determined by the number of assets to be serviced and the amount of time in which they are to be serviced.
- A single agent may service approximately 100 assets every 12 hours, depending on network loading, asset programming, and so on.
Product Version | Agents | Remote Agents |
|---|---|---|
16.00 | 100 This is a sum of local and remote agents. | 50 |
15.00 | 100 This is a sum of local and remote agents. | 50 |
13.00 | 50 | Not supported |
12.00 | 50 | Not supported |
11.00 | 50 | Not supported |
10.00 | 50 | Not supported |
9.00 | 35 | Not supported |
8.00 | 25 | Not supported |
7.00 | 15 | Not supported |
6.00 | 15 | Not supported |
5.00 | 5 | Not supported |
Where will the agents be installed?
- For recommended system requirements, see theFactoryTalk AssetCentre Installation Guide.
- It is supported but not recommended to install an agent on an engineering workstation due to the frequent processing requirements, as well as complications with secured editors.
- It is possible to co-locate an agent on the FactoryTalk AssetCentre server, depending on the system resources of the server computer and the size of the system, that is the number of assets the agent will service and the number of FactoryTalk AssetCentre clients the server will service. It should be monitored after installation to ensure no performance degradation.
- In version 5.00 or earlier, if using Disaster Recovery, all agents must have the same communications path to all assets.
Do the agents have all the required software packages?
- In version 5.00 or earlier, each agent must be configured identically. This means that the required software packages must be installed on all agents.
- An agent performing Disaster Recovery operations must have the matching communication and editing software for that asset installed locally. For example, ControlLogix requires RSLogix 5000 and RSLinx Classic.
- These software packages do not require activation, except for Drive Executive.
Is there other FactoryTalk software in the system?
- Ensure that all software is capable of running on the same FactoryTalk Services Platform major version. For example, CPR9.
- If audits are required from these FactoryTalk software packages, a FactoryTalk AssetCentre client must be installed locally. Additionally, these software packages must be in the same FactoryTalk Directory as the FactoryTalk AssetCentre server.
- The exception to this is for PanelView Plus family terminals running FactoryTalk View Machine Edition, which can be configured for remote diagnostic and audit logging.
For more information about architecting FactoryTalk AssetCentre, see Knowledgebase Document ID: QA6409 - Architecting FactoryTalk AssetCentre.
For more information about system design considerations, see Knowledgebase Document ID: QA11498 - FactoryTalk AssetCentre System Design Considerations.
Provide Feedback