FactoryTalk AssetCentre Asset Inventory frequently asked questions

What is the FactoryTalk AssetCentre Inventory Agent?

Introduced in version 7.00, FactoryTalk AssetCentre can now be used to collect information on an entire system of assets. Using CIP, SNMP, and WMI scanning, the Inventory Agent will build a list of automation devices, network devices, and Windows Operating Systems.

These lists can be used to maintain up-to-date system information, including synchronization of the FactoryTalk AssetCentre tree itself.

For a video demonstration of the functionality, see https://www.youtube.com/watch?v=69ZPRPGCnLk&list=PL3K_BigUXJ1NLQyp5q1DEbOw16kki5JWP&index=4.

Does the FactoryTalk AssetCentre Inventory Agent require a license?

Yes. The FactoryTalk AssetCentre Inventory Crawler requires the

Disaster Recovery - Asset Inventory

capability license.

The catalog number for the FactoryTalk AssetCentre Asset Inventory Agent is

9515-ASTDRINVENE

. The Asset Inventory Agent is part of the FactoryTalk AssetCentre System Starter kit

9515-ASTSRVSTENE

.

How is the FactoryTalk AssetCentre Inventory Agent related to FactoryTalk AssetCentre Disaster Recovery?

The Inventory Agent scans are scheduled operations, which are managed by the Disaster Recovery functionality of FactoryTalk AssetCentre. The Inventory Agent is a separate asset type from any other Disaster Recovery tasks, meaning that no other Disaster Recovery functionality is required.

What types of inventory scans can be performed?

How do I install the FactoryTalk AssetCentre Inventory Agent?

The FactoryTalk AssetCentre Inventory Agent is installed during the FactoryTalk AssetCentre Agent installation.

How do I configure the FactoryTalk AssetCentre Inventory Agent?

A new Asset Inventory asset type is now available to be added to the asset tree. Each Asset Inventory asset can support up to one of each scan type. In general, it is recommended to configure a new asset for each scan instead of combining multiple scan types into one asset.

Once the asset is configured, it must be added to a Disaster Recovery schedule to be executed.

When the scan completes, it will return a *.RAAI file with the scan results and, if configured, a differences report based on the last time the scan was executed. If the scan is running for the first time, it will automatically add a new *.RAAI file to the asset tree.

What is an RAAI file?

An RAAI file, or Rockwell Automation Asset Inventory file, is the file produced from running a schedule for an Asset Inventory asset. This file contains a list of the devices and software that was discovered as part of the scan.

How is an RAAI file used?

This file is used by the FactoryTalk AssetCentre agent during Disaster Recovery Backup and Compare schedules to compare the previously discovered network devices and software with the results of the new scan.

The RAAI file can be viewed from within the FactoryTalk AssetCentre desktop client, using the Asset Inventory Grid View program. When opened within the AssetCentre desktop client, an RAAI file can be used to update and maintain the asset tree. Discovered assets that already exist within the asset tree can be updated if their properties change, and newly discovered assets can be added directly to the tree. In FactoryTalk AssetCentre version 15.00, the RAAI file can also be viewed from within the FactoryTalk AssetCentre Inventory Viewer without installing the FactoryTalk AssetCentre desktop client. For more information, see FactoryTalk AssetCentre Inventory Viewer Help.

The RAAI file can also be exported to XML.

As of version 7.10, FactoryTalk AssetCentre Asset Inventory CIP scan results can also be integrated with the Product Compatibility and Download Center website (PCDC) to obtain product compatibility, firmware downloads, and lifecycle status. 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.

In FactoryTalk AssetCentre version 8.00, this information can now be viewed in the FactoryTalk AssetCentre desktop client through the Assets Lifecycle view. For additional information and frequently asked questions, see Knowledgebase Document ID: FAQ: QA40307 - FactoryTalk AssetCentre Assets Lifecycle.

Can the FactoryTalk AssetCentre Inventory Agent be used across multiple subnets?

Yes. The FactoryTalk AssetCentre Inventory Crawler can be used to scan across multiple subnets, provided they are properly routed.

Is RSLinx Classic required?

Yes, for CIP scans. The Asset Inventory Agent uses RSLinx Classic to scan for CIP devices, meaning uniform drivers and connectivity across agents in the group is required. SNMP and WMI scans do not use or require RSLinx Classic.

What types of devices can be discovered using the CIP scan?

An Asset Inventory CIP scan is configured to use an RSLinx Classic driver, and will return all devices available on this driver, including controllers, Ethernet modules, communications modules, input and output modules, drives, and so on. Because the device must be discoverable by RSLinx Classic, many non-Rockwell Automation assets will not be returned by a CIP scan.

Will a CIP scan discover bridged assets?

Yes. RSLinx Classic can be configured to scan remote subnets by routing through a Logix 5000 backplane. Once this configuration is completed, a FactoryTalk AssetCentre Asset Inventory CIP scan will discover the devices that are configured for remote browsing. When performing a CIP scan with an Ethernet/IP, predicting the depth level of discoverable bridged assets can be difficult. Given that the CIP imposes a depth limitation of seven levels, we recommend creating additional Asset Inventory disaster recovery schedules to ensure the capture of more devices if you are using an Ethernet/IP to perform a CIP scan. While it is possible to exceed seven levels when bridging to different networks using DeviceNet or ControlNet, the actual depth level depends on the specific network structure.

What type of information is returned by a CIP scan?

Catalog Information, Device Name, Device Address, Hardware Revision, Manufacture Date*, MAC Address, Network Node Type, Network Type, Product Code, Product Name, Product Type Code, Product Type, Program Name, Path, Revision, Serial Number, Series*, Vendor ID, and Warranty Number*.

Items marked with an asterisk (*) are enhanced CIP identity objects, which are only retrievable for devices that are manufactured after the enhanced CIP identity object is introduced.

Are there any CIP scan performance considerations?

Yes. Legacy networks like DH+, DNET, and so on will take longer to scan than Ethernet networks. It is recommended that a test environment be used to determine performance effects prior to running the scan within a production environment. When performing a CIP scan with an Ethernet/IP, predicting the depth level of discoverable bridged assets can be difficult. Given that the CIP imposes a depth limitation of seven levels, we recommend creating additional Asset Inventory disaster recovery schedules to ensure the capture of more devices if you are using an Ethernet/IP to perform a CIP scan. While it is possible to exceed seven levels when bridging to different networks using DeviceNet or ControlNet, the actual depth level depends on the specific network structure.

For more information, see Knowledgebase Document ID: QA37407 - FactoryTalk AssetCentre Asset Inventory Considerations.

What type of devices can be discovered using an SNMP scan?

Those devices that communicate using SNMP (Simple Network Management Protocol) will respond to the Asset Inventory SNMP scan. These devices include, but are not limited to network switches, routers, servers hosting virtual machines, and so on.

What type of information is returned by an SNMP scan?

Device Address, Device Identity, Device Owner, Firmware Revision, Host Name, MAC Address, Model Name, Model Serial, and SNMP Device Description.

What information is needed for my SNMP scan to be successful?

The SNMP Community string configured in the devices on the network is needed. A single community string can be entered for each scan, meaning that all devices in the scan range must use the same community string. If multiple community strings are in use, multiple scans must be configured. The community string is configured using the asset's Advanced Settings menu.

Are there any SNMP scan performance considerations?

Yes. Consider adjusting the SNMP timeout based on performance testing. The scan will iterate through each IP address in the configured scan range, first sending a ping, then an SNMP get request to any address that responds to the ping. The scan will then wait the length of the timeout for an SNMP get response. If a device does not support SNMP, it will not respond, resulting in the timeout expiring. In many cases, the default 60-second timeout can be reduced to allow for quicker scanning.

For more information, see Knowledgebase Document ID: QA37407 - FactoryTalk AssetCentre Asset Inventory Considerations.

What version of SNMP is supported?

The FactoryTalk AssetCentre Inventory Crawler uses SNMP v2.

What type of information is returned by a WMI scan?

The WMI (Windows Management Instrumentation) scan will connect to the local and remote computers in the IP Range specified, using the supplied credentials and collect information pertaining to the software installed on that machine. This information includes: Name, Install Date, Vendor, and Version.

What information is needed for my WMI scan to be successful?

Domain credentials with elevated permissions allowing WMI access.

Are there any WMI scan performance considerations?

Yes. Consider adjusting the WMI timeout based on performance testing. The scan will iterate through each IP address in the configured scan range, first sending a ping, then a WMI request to any address that responds to the ping. The scan will then wait the length of the timeout for a WMI response. If a device does not support WMI, it will not respond, resulting in the timeout expiring. In many cases, the default 60-second timeout can be reduced to allow for quicker scanning.

For more information, see Knowledgebase Document ID: QA37407 - FactoryTalk AssetCentre Asset Inventory Considerations.

Is there a service required for the FactoryTalk AssetCentre Inventory Agent?

A new service is installed for the FactoryTalk AssetCentre Inventory Agent operations, FactoryTalk AssetCentre Inventory Crawler Server.

Can the Inventory Crawler be used to add Allen-Bradley PanelView Plus assets to the FactoryTalk AssetCentre configuration?

Yes. While RSLinx Classic is used to scan for CIP devices, an Allen-Bradley PanelView Plus asset can still be added to the asset tree. Allen-Bradley PanelView Plus assets will be added with all of the returned CIP information, but without a device address.

The address can then be added using an RSLinx Enterprise browse, as with a normal asset addition.

Are there additional fields available that I can use to keep track of additional asset information in a .RAAI file?

Yes. A commission date and three

Additional Information

fields are available in the new FactoryTalk AssetCentre Inventory Crawler. The names of these fields can be modified using the

Tools > Options

menu in the FactoryTalk AssetCentre desktop client, then selecting

Asset Inventory

from the left pane.

These settings are global, changing them will affect Asset Inventory scans that were saved previously. These fields can be used to track location of the asset in the plant, EM responsible for maintenance of the asset, and other specific fields found useful by the FactoryTalk AssetCentre users. To view these fields in the Asset Inventory Grid View program, the columns must be enabled through the

Columns

menu.

Can the CIP, SNMP, and WMI timeout settings be modified globally?

Yes. By accessing the

Tools > Options

menu, then selecting Asset Inventory from the left pane, the Advanced Settings configuration can be viewed. These modifications will only take effect for new Asset Inventory configurations. Existing configurations will keep their previous configurations. Modifications to the configuration of existing Asset Inventory assets can only be made to those individual configurations.

How are diagnostic messages logged from the FactoryTalk AssetCentre Inventory Crawler?

Log4net is used to log diagnostic messages. Logs can be located in the following locations.