Tune the Historian primitive in platforms and engines

• Set deadbands for parameters of data to historize.

• Increasing the deadband decreases the network traffic.

• Do not enable the Historian component in WinPlatforms and AppEngines unless they will actually be hosting objects with attributes to be historized.

• Do not enable the Historian feature in the highest level template for any object because this forces historization of every instance. Selectively apply the Historian feature to some templates and to specific instances of objects.

• Modify the Historian tuning constants which are attributes of the Engine component found in the WinPlatform and AppEngine objects.

  Note: The following attribute default values are designed for a non-intermittent network environment and are especially important in a widely-distributed, redundant system.

You can increase the StoreForwardMinDuration value to force the host computer to function in "Store" mode for a longer time. This prevents the computer from trying to re-connect to the Historian prematurely. The longer duration allows time for any network issues to resolve themselves.

For the occasions that communications with the Historian are interrupted, local storage and recovery of historical data is provided. It is important to configure the historization parameters of the AppEngine object using the IDE to accommodate the number of packets that will be transmitted over the network when data is being restored.

Be sure enough disk space is on the local node to temporarily store data until it can be transferred to the historian.