Release Notes - Version 4.2


Below, an overview is provided of the improvements that have been included in version 4.2 of the Alignability® Process Model. Minor changes (e.g. improvements of the layout or spelling corrections) are not listed.

Version 4.2  -  February 2006

No.

Description of Improvement

Configuration Management

1.

Changed Configuration Management work instructions 2.8.1, 3.2.2, 3.3.2, 3.5.2, and 4.4.1 to take account of the fact that the Site and Address forms have been combined into a single form.

2.

Added the Planned downtime field just below the Status field on the Configuration Item form.

3.

Combined the Category and Subcategory fields and configured a user interface rule to ensure that a second level category needs to be selected when available.

4.

Placed the Parent CIs, the Component CIs and the Related CIs field on a new page called "CI Relations" to reduce the number of tab pages of the Configuration Item form.

5.

Combined the Problems page and the Work Orders page on the Configuration Item form into a single page called "Problems & Work Orders" to reduce the number of tab pages.

6.

Added the Metrics page to the Configuration Item form.

7.

Added the checkbox field "Blocked" to the Contract form. This field is only visible for system administrators. It will be checked by a scheduled database rule when expiry date of the contract has been reached. The check will be removed when Expiry date field has been set to a future date.

Alarm Management

8.

Added the Services field to the Alarm form. This field lists the services that are linked to the CI for which the Alarm was registered. Adjusted Alarm Management work instruction 1.4.4 and 1.7.4 (including the note that follows these instructions) to make use of this new feature. Also adjusted the very last note of the work instructions for Alarm Management step 1.4 for the same reason.

Incident Management

9.

Swapped the position of the Tracking & Finance page and the Relations page on the Support Request form. Placing the tracking information closer to the History page makes the form layout more logical.

10.

Replaced all occurrences of "service hours" with "support hours" in field utilization guidelines for the Support Request form.

Problem Management

11.

Swapped the position of the Tracking & Finance page and the Relations page on the Problem form. Placing the tracking information closer to the History page makes the form layout more logical.

Change Management

12.

Added the Change Management KPI "Emergency changes".

13.

Renamed the Affected CIs page of the Work Order form to "Affected Organizations & CIs" and moved the Impacted org. field to the top of this page.

14.

Renamed the Impacted org. field of the Work Order form to "Affected org." to make it clearer that the effect is not necessarily negative (i.e. it could concern an improvement of the functionality without causing a service degradation or outage).

15.

Added a database rule that ensures that the Affected org. field must be filled out after an outage has been specified on the Affected Organizations & CIs page on the Work Order form.

16.

Replaced the Downtime field with the Outage start date field and the Outage start date field. These two new fields have been added to the bottom of the Affected Organizations & CIs page on the Work Order form.

17.

Rewrote the work instructions for Change Management steps 2.5, 5.5 and 6.7 to take account of the adjustments of the Work Order form. Removed Release Management work instructions 2.10.2, 3.3.4, 3.10.4, 3.11.4, 4.1.2, 4.9.3 and 4.10.2, and Continuity Management work instructions 5.1.9 and 5.3.3 for the same reason.

18.

Moved the position of the Tracking & Finance page to just before the History page on the Work Order form. Placing the tracking information closer to the History page makes the form layout more logical.

Release Management

19.

Renamed the Changes page of the Release form to "Details" to be consistent with the Support Request, Problem, Change and Work Order forms. Updated Release Management work instructions 2.9.5 and 4.2.3 accordingly.

20.

Moved the Status field of the Release form to the top of the Details page to be consistent with the Support Request, Problem, Change and Work Order forms.

21.

Moved the Completion code field of the Release form to the Details tab, just below the Status field to give this field a position that is more consistent with its position on the Support Request and Change forms. Placed a separator below this field.

Service Level Management

22.

Added the Service Definition form.

23.

Added the Configuration Item Definition form.

24.

Renamed the BIL form to "Service Level".

25.

Added the checkbox field "Blocked" to the Service form. This field is only visible for system administrators. It will be checked by a database rule when the status of a service is either "Being Developed" or "Discontinued".

26.

Added the Customers page to the Service form. The following fields have been placed on this page:

Persons

Organizations

Sites

27.

Added the Service Hierarchy page to the Service form. The following fields have been placed on this page:

Hierarchy status

Service Hierarchy

28.

Added the Service Levels page to the Service form. The following fields have been placed on this page:

Status per SLA

Metric Status per SLA

29.

Added the SLOs page to the Service form. The following fields have been placed on this page:

Metric Thresholds

Compliance Thresholds

Service SLO's Availability

30.

Added the Metrics page to the Service form. The following fields have been placed on this page:

Definition

Conform definition

Propagation rule

Metric details status

Service Metrics

SN status

SN name

SN server

31.

Added the checkbox field "Blocked" to the Service Level Agreement form. This field is only visible for system administrators. It will be checked by a database rule when the status of a service level agreement is either "Being Developed" or "Discontinued".

32.

Renamed the BIL field of the Service Level Agreement form to "Service level". This was done, because the business importance level (BIL) is now selected on the Service Level form.

33.

Replaced the Service field of the Service Level Agreement form with the Services field. This field, which can be used to link multiple services to the SLA (even though this is not recommended), has been placed on the new Services & Roles page.

34.

Replaced the Representative field of the Service Level Agreement form with the Roles field, which has been placed on the Services & Roles page.

35.

Added the Sites field to the Customers page of the Service Level Agreement form.

36.

Added the Support Requests field and the Support Hours per Impact Level field to the new Support page of the Service Level Agreement form.

37.

Rearranged the Metrics page of the Service Level Agreement form. The following fields have been placed on this page:

Management status

Activity status

Evaluation period

Compliance status

Time of compliance

Predicted status

Time of prediction

OVSD Metrics

OVIS Configuration

The OVSD field has replaced the Incident resolution field, the Reliability field and the Service Desk Metrics field.

38.

Added Service Level Management work instruction 1.8.4 to make use of the new ability to maintain a service catalog inside the in HP OpenView Service Desk 5.0 application.

Glossary

39.

Split the glossary definition of the term "Service hours" into "Service hours" and "Support hours" to allow for this distinction in HP OpenView Service Desk 5.0.

General

40.

Combined the Site form and Address form into a single form.

41.

Replaced the Addresses field on the Organization form with the Sites field. This field has been placed on the main page, rather than the Addresses page of the form.

42.

Moved the Web sites field from the Addresses page to the bottom of the Details page of the Organization form.

43.

Removed the Addresses page from the Organization form.

44.

Added the Requests page to the Organization form. Placed the Support Requests field on this new page.

45.

Added the Services & SLAs page to the Persons form. The following fields have been placed on this page:

Customer of the Following Services

Customer of the Following SLAs

Performs Roles for the Following SLAs

46.

Added the Performs Roles for the Following Services field to the Service Desk User Details page below the Groups field.