This documentation applies to the 8.1 version of Service Level Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Creating milestones for an agreement

You can create milestones and a set of actions that trigger if your compliance target is at risk or is breached. Milestones are optional.

To create a milestone for an agreement

  1. Log on to the Service Level Management Console.
  2. Click the Agreements tab and select an agreement.
  3. Click View.
  4. Click the Milestones tab.
  5. Click Add to display the Create New Milestone dialog box.
  6. In the Select field, choose Custom > New Milestone.
    The Milestone For agreementName dialog box appears.
  7. Enter a title for the milestone.
    Do not include any parentheses in the milestone title.
  8. Enter an optional description.
  9. Select a review period to which you want the milestone to apply.
    The review period must reflect one of the review periods created in the Review Periods/Penalty Rewards tab.
  10. Select a qualifying statement from Execute If list. The options are:
    • Compliance At Risk — The milestone action is triggered if the percentage compliance reaches the Compliance At Risk percentage, as specified on the Related Service Targets tab.
    • Compliance Target Missed — The milestone action is triggered if the compliance target is not met, as specified on the Related Service Targets tab.
    • Compliance Is Less Than — The milestone action is triggered if the percentage compliance is less than the amount you specify in the % field.
  11. Click OK to return to the Milestone tab.
    Your milestone appears in the Milestones table with the build status.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Andrej Kajzer

    Should be milestone name unique value?

    Dec 13, 2013 06:57
  2. Surabhee Kulkarni

    Thank you for your comment. As per my discussion with the developer, since the milestone instance ID is unique, it is not necessary for the milestone name to be unique.

    Dec 16, 2013 04:19