Configure an appropriate committed point in time and an appropriate alert margin threshold for a baseline -

Background information

A baseline can help you identify an exception that prevents a node in the baseline from being completed as expected and send you an alert notification about the exception at the earliest opportunity. This ensures that the data that you want to obtain is generated as expected in scenarios in which dependencies between nodes in the baseline are complex. For more information, see Overview.
The committed point in time for a baseline is the time before which nodes in the baseline are committed to finishing running. DataWorks ensures that all nodes in a data application finish running before the committed point in time. If you want to reserve a certain amount of time for O&M personnel to handle exceptions that occur on nodes in a baseline, you can configure an alert margin threshold for the baseline. The system uses the time obtained by subtracting the alert margin threshold from the committed point in time as the alert time of the baseline. The alert time is also the estimated time before which all nodes in the baseline finish running.
For more information about how to configure a committed point in time and an alert margin threshold for a baseline, see Manage baselines.

Limits

Only DataWorks Standard Edition and more advanced editions support the baseline management feature. If you use DataWorks Basic Edition, you must upgrade DataWorks to DataWorks Standard Edition or a more advanced edition before you can use the baseline management feature. For more information, see Differences among DataWorks editions.

How to configure an appropriate committed point in time and an appropriate alert margin threshold for a baseline

Calculate the estimated latest completion time for a baseline based on the latest completion time of nodes in the baseline within a historical period of time, and set the committed point in time for the baseline to a point in time later than the estimated latest completion time. In addition, you must reserve a specific amount of time as an alert margin threshold when you configure the committed point in time. This way, if you receive an alert notification, you can have sufficient time to finish handling exceptions that occur on nodes in the baseline before the committed point in time arrives. Configure an appropriate committed point in time and an appropriate alert margin threshold

Sample scenarios in which an inappropriate committed point in time or alert margin threshold is configured for a baseline

If the committed point in time or alert margin threshold that you configure for a baseline is inappropriate, the baseline may enter the Overtime state, and the alert that is reported for the baseline may not meet your requirements.

Scenario 1: The committed point in time for a baseline is the same as the estimated latest completion time, and no alert margin threshold is configured for the baseline.
In this scenario, if an exception occurs on a node in the baseline, the baseline may enter the Overtime state, and alerts are frequently triggered because no alert margin threshold is specified.
Scenario 2: The alert margin threshold that you configure for a baseline is inappropriate. For example, the alert time (obtained by subtracting the alert margin threshold from the committed point in time) for the baseline is earlier than the estimated latest completion time.
In this scenario, if an exception occurs on a node in the baseline, the baseline may enter the Overtime state, and alerts are frequently triggered because the value of the alert margin threshold is small.
Scenario 3: The committed point in time that you configure for a baseline is inappropriate. For example, the committed point in time for the baseline is earlier than the estimated latest completion time.
Nodes in the baseline cannot finish running before the committed point in time arrives. The system sends you an alert notification on 00:00:00 on the current day.