Related Products:

EMMK-101, EMMK-102, EMMK-103

Related Documents:

ISCM-0380, ISCM-0385

Type:

Maintenance

Keywords/Labels:

calendar-based aging, configuring, preserving data

Summary:

This article describes aging strategies, configuring an aging strategy, and preserving data.

Aging Strategies

An aging strategy prompts the server to delete historical data if certain conditions are met.

Systems with many devices or with devices performing frequent acquisitions can require significant disk space to store data. InsightCM provides features for automatically discarding data events after configurable conditions are met. This automatic process, called aging, conserves disk space while maintaining a desirable collection of data.

InsightCM applies the periodic aging strategy to individual data events that are not part of a stream. The streaming aging strategy is used to discard entire streams. InsightCM does not retain partial streams.

After the daily aging strategy runs, InsightCM retains a maximum of one trend point per hour, excluding streams. If a data event contains a data set and a trend point, InsightCM counts that as the trend point for that hour and deletes all other trend points.

Note

InsightCM ignores periodic data events triggered by an alarm transition and never deletes them due to aging.

Calendar-Based Aging Strategy

A calendar-based strategy enables you to determine which and how much data to discard. This strategy follows a time-based schedule to discard data events after a configurable number of days. You can configure the strategy to discard all data sets except those collected at a specific time. For example, you can retain some data to trend over an extended period of time by configuring a calendar-based strategy that deletes all periodic data events except those collected at 12:00pm after two days elapse.

You can also choose to retain data events that have alarms or comments associated with them and exclude data events from a particular operating state.

Note

The aging strategy runs every fifteen minutes, so InsightCM might not discard data immediately after the aging condition is met.

calendar-based strategy

Identifying Data that Is Exempt from Aging

You can identify data that InsightCM exempts from aging on the Trend viewer. The Trend viewer shows data points from times that are exempt from aging rules. For example, if InsightCM is configured to delete all periodic data three days after collecting it, but the Trend viewer displays a value that is five days old, that data point is exempt from aging.

calendar-based strategy

Configuring an Aging Strategy

Conserve disk space by configuring a strategy that automatically deletes historical data when certain conditions are met.

To learn more about the periodic and streaming aging strategies, refer to Aging Strategies. Complete the following steps to configure an aging strategy.

  1. Click Navigation menu (noloc_env_navmenu.png) and select Options.

  2. Navigate to Server Settings.

  3. Select Periodic Aging Strategy or Streaming Aging Strategy.

    Note

    Both periodic and stream aging strategies are system-level strategies that apply to data events from all devices.

  4. Use the Aging Strategy pull-down to select the Calendar-Based strategy.

  5. Use the text box below the pull-down to specify how many days' worth of data events to retain.

  6. Specify time(s) when the device permanently retains the data events it collects.

  7. Use the corresponding checkboxes to configure whether data events collected with alarms or for all MCSA Startup events are always retained and whether to retain burst data sets.

  8. Use the Never retain data events from pull-down and select an operating state.

  9. Click OK.

The following table compares how two different aging strategies operate on data. In these examples, assume Day 1 begins with zero data events.

Strategy

Day 1

Day 2

Day 3

Collect

Delete

Total Stored

Collect

Delete

Total Stored

Collect

Delete

Total Stored

Calendar-based—Retain from the past two days

3

0

3

3

0

6

4

All 3 collected on Day 1

7

Calendar-based—Retain from the past two days, and then permanently retain the data event collected at 12:00 PM every day

3

0

3

3

0

6

4

All collected on Day 1 except the one collected at 12:00 PM

8

The calendar-based strategy in the second row is useful when you want to access all acquired data only during the recent past. For example, if an equipment asset fails, you may want to review data from every acquisition that occurred 2 days prior to the failure. However, you may only need to view data from one acquisition per day twenty days prior to failure.

Now that you have configured an aging strategy, learn how to preserve some data events from aging strategies.

Calendar-basedCalendar-based

Preserving Data from Aging Strategies

Ensure data from a specific acquisition remains available for viewing regardless of aging rules.

Before you begin, you need to have acquired data.

Feature and sensor data remains accessible whenever the Trend viewer time-axis contains the time at which the acquisition occurred. When you choose to retain data, InsightCM retains all the data associated with the sensor acquisition, such as feature values, the time waveform, and other measurements, such as the FFT curve.

Complete the following steps to identify which data events you want to retain.

  1. Click the Navigation menu (noloc_env_navmenu.png) and select System > Data Events.

  2. In the Data Events dialog, select an equipment asset from the asset tree to bring up corresponding log data events on the right.

  3. Select the data event of interest that contains data sets.

  4. Click Retain.

    Note

    Remove the retain property by selecting a data event marked for retention and clicking Retain.

  5. Click OK.

  6. Verify that the data event has been marked for retention.

    Note

    Click the Action menu (noloc_env_action.png) above the data events log and select Export to export a TDMS file for a data event.

Do you need more help?

calendar-based strategy Calendar-basedCalendar-based
Was this article helpful?
0 out of 0 found this helpful

Articles in this section