FactoryTalk Historian ME storage capacity
The FactoryTalk Historian ME module has 2 GB of total storage. It has an effective archive storage capacity of 1.5 GB.
There are the archive file size limits:
- File size: 10 MB
- Number of files: 130
- Disk space for archives: 1.3 GB
The onboard data storage for FactoryTalk Historian ME is limited. When you use a data collection rate of 2500 events per second (that is, the maximum collection rate available) without compression or exception filtering, the onboard storage capacity is approximately 14 hours. Therefore, it is highly recommended that you include the FactoryTalk Historian SE or PI server for data aggregation when long-term storage is required. By applying compression and exception filtering, you can significantly increase the archive space from approximately two to ten times, depending on variables (for example, how much the data varies between scans). To estimate the archive performance with and without compression and exception filtering, you can use a typical factor of five. For more information on compression and exception filtering, see Filter data.
Use the following table to estimate the performance impact. Note that the data storage information in this table is an estimate. The actual compressed data storage ranges will vary depending on the volatility of the data collected.
Sample Application | Estimate |
|---|---|
2500 events per second without Compression or Exception Filtering | 14 hours |
2500 events per second with Compression and Exception Filtering | 3 days |
500 events per second with Compression and Exception Filtering | 2 weeks |
100 events per second with Compression and Exception Filtering | 3 months |
2500 events per minute without Compression or Exception Filtering | 1 month |
2500 events per minute with Compression and Exception Filtering | 6 months |
500 events per minute with Compression and Exception Filtering | 2.5 years |
100 events per minute with Compression and Exception Filtering | 10+ years |
To calculate the total events per second, the tags divided by the scan rate have to be summed up per scan class for the module:

For example, if the data collection configuration is based on two scan classes (one with
200 tags at a 250 ms scan rate, and one with 600 tags at a 2 s scan rate), the total events
per second are 1100.
200/250ms + 600/2sec <-> 200/.25sec + 600/2sec <-> 800 + 300 events/sec = 1100 events/sec
Provide Feedback