Configuring classification settings for release templates

You can specify values in a release template's Classification tab to add information to the corresponding Classification tab in the Release form.

The Classification tab is used to describe the release and show which products or services are affected by the release. The Impact, Urgency, and Risk Level values are required before a release can be submitted.

To configure classification settings

1. From the Application Administration Console, click the Custom Configuration tab.
2. From the Application Settings list, choose Release Management > Template > Template, then click Open.
   The Release Template form appears.
3. In the Template Name field, enter a name for the template.
4. In the Status field, select an appropriate status level for this template.
5. Click the Classification tab.
   
   Release Template form — Classification tab
   
   
   
6. In the Impact field, select an impact level for the release request (for example, 1-Extensive/Widespread).
7. In the Urgency field, select a level of urgency for the release request (for example, 1-Critical).
8. In the Priority field, select a priority according to the urgency of the release request (for example, Medium).
9. In the Risk Level field, select a value. Risk Level 5 is the highest risk and Risk Level 1 is the lowest.
10. In the Summary field, enter a brief description of the release request. This information will be entered into the Summary field on the Release form.
11. In the Notes field, enter a detailed description of the release request.
12. In the Release Type field, select an area for the release request (for example, Delta).
13. In the Service field, select a business service CI.
    After you select a business service CI, the product categorization from the business service CI is copied over to the Product Categorization Selection fields of the release template (under the Categorization tab). You can overwrite this data. In addition, after you save the release template, an association is created between the business service CI and the release template. You can change or delete the business service CI, and you can manually remove the association from the Relationships table.
14. In the Deployment type field, select the deployment type for the release request:
    • Phased — Stage the deployment of the release to a part of the user base. The operation is repeated for subsequent parts of the user base through a scheduled rollout plan. For example, the release coordinator identifies a set of changes that must be done at the same time: all changes for Building 1 at Phase 1, all changes for Building 2 at Phase 2, and so on.
      You typically use phased deployments when new services are introduced into a store environment in manageable phases (such as retail organizations).
    • Non-Phased — All changes or activities are deployed at the same time in one operation with no restrictions (for example, a company-wide rollout of new servers).
      You typically use non-phased deployments when introducing an application change, and consistency of service across the organization is important.

      Note

      IT Infrastructure Library (ITIL) Service Transition Version 3 describes non-phased deployment as the Big Bang method.

15. In the Company field, select the name of the company for this release request.
16. In the Region field, select the area of the company.
17. In the Site Group field, select the city of the company.
18. In the Site field, select the location of the company for this release request.
19. Click Save.