Remote Collectors

In AIM, each instance can use one or more remote collectors. Remote collectors are used to distribute the AIM historian architecture or to obtain data from sources other than Foxboro Evo controllers (e.g. via OPC) or both.

In FAIM, remote collectors have no real meaning. FAIM supports distributed data collection via the simulation network and is capable of storing data from non-Foxboro Evo sources directly.

By default, FAIM attempts to locate and store data for every RTP in a historian instance configuration, regardless of its configured collector, using the NAMEINCOL parameter of a point configuration as a symbol lookup into the current simulation.

In most circumstances, the default functionality is acceptable, but in some, the data collection for all RTPs in one instance is not required. For example, when one off-platform AIM*Historian instance is configured to retrieve data from multiple Foxboro Evo systems, but only one of the Foxboro Evo systems is being simulated. To support this situation, FAIM supports disabling data collection for specifically named remote collectors. Configuration of collectors is disabled via the ignorecol engine configuration parameter.