This documentation applies to the 8.1 version of Change 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.

Adding classification information

Classification information is used to describe the business justification of a request (for example, Sarbanes-Oxley requirements) and show which products and services are affected by the request. This information can be helpful when the request goes through the approval process.

To enter classification information when using the Best Practice view

  1. On the Change form, click the Categorization tab.
  2. Enter the following information:

    Field

    Description

    Class

    Define the urgency of the change (for example, Normal). For more information, see Creating a change request at the initiate stage - Best Practice view.

    Change Reason

    Define the business reason for implementing the change request.

    Available options include:
     - Upgrade
     - New functionality
     - Maintenance
     - Upgrade
     - Other 

    If the request needs to go through the approval process, change reason information can be helpful.

  3. Choose Links > Categorizations and enter the following information:

    Field

    Description

    Operational Categorization

    Operational categorization is based on a three-tier hierarchy that is configured in the Operational Catalog.

    Product Categorization

    Product categorization is based on a five-tier hierarchy that is configured in your Product Catalog.

  4. Click Save.

To enter classification information when using the Classic view

  1. On the Change form, click the Classification tab.
  2. Enter the following information:

    Field

    Description

    Class

    Define the urgency of the change (for example, Normal). For more information, see Creating a change request at the Initiate stage - Classic View.

    Timing Reason

    Define the reason for creating a change request with a Timing of Expedited (for example, Insufficient lead-time). For more information, see Plan and Schedule stage - Planning the change request.

    Lead Time

    Define the amount of time that you need to prepare for a change implementation.

    The system adds Lead Time to the Submit date to determine the Earliest Start date and time. For example, if the Submit date is 5/18/2010 1:50:29 A.M. and you type 8 in the Lead Time field, the system determines that the Earliest Start Date is 5/18/2010 9:50:29 A.M.

    Note: The Lead Time field is available only from the Classification tab of BMC Change Management Classic view.

    Change Reason

    Define the business reason for implementing the change request. Available options include:
     - Upgrade
     - New functionality
     - Maintenance
     - Upgrade
     - Other

    If the request needs to go through the approval process, change reason information can be helpful.

    Business Justification

    Tracks the business reason for request.

    Available options include:
     - Corporate Strategic
     - Business Unit Strategic
     - Maintenance
     - Defect
     - Upgrade
     - Enhancement
     - Customer Commitment
     - Sarbanes-Oxley

    Note: Select an option based on the classification defined by your company.

    Change Environment

    Define the environment where the change will be implemented.

    Available options include:
     - Upgrade
     - New functionality
     - Maintenance
     - Upgrade
     - Other 

    This field is useful when mapping approvers and for reporting purposes. An approver can be mapped for a selected environment.

    Sequence

    Define whether you want the change request to take place in a particular order relative to other change requests. For more information, see Planning dependencies for change requests.

    Performance Rating

    Rate the work done by support staff or the manager in completing the change request.

    Note: Do not enter information into the Performance Rating field when you are creating a change request. The manager of the support staff assigned to the change request typically enters this rating after the change request reaches the Completed status. For more information, see Closed stage - Completing change requests.

    Notes

    Define a more detailed description of the change request.

    Operational Categorization

    Operational categorization is based on a three-tier hierarchy that is configured in the Operational Catalog.

    Product Categorization

    Product categorization is based on a five-tier hierarchy that is configured in your Product Catalog.

  3. Click Save.
Was this page helpful? Yes No Submitting... Thank you

Comments