Change Data Object


The Change data object includes details of a proposed Change to one or more CIs.

Key Attributes

The Change data object shall have the following key data attributes:

  • Id: unique identifier for the Change record

  • Title: title of the Change

  • Description: description of the Change

  • Category: classify and define the type (emergency, standard, normal, etc.) of Change requested; each category has its own lifecycle

  • Approval Status: current status of the Change approval

  • Risk: the probability that the Change could cause harm or loss, or affect the ability to achieve objectives

  • Planned Start Time: date/time when the Change implementation is planned to start

  • Planned End Time: date/time that Change implementation is planned to end

  • Assigned To: actor that is assigned to implement the Change

Key Data Object Relationships

The Change data object shall maintain the following relationships:

  • Change to Order (1:n): receives Change request and Change request status

  • Change to Desired Product Instance (1:n): acquires relevant information about the Desired System(s)

  • Change to Pipeline (n:1): the Pipeline supplies the Change Orders with information needed to instantiate the service

  • Change to Change (n:m): a Change can depend on other Changes that have been delivered, or it can be decomposed into a number of more fine-grained Changes

  • Incident to Change (n:1): tracks the Incident(s) caused by the Change

  • Change to Incident(1:n): tracks the Incidents that needs emergency Changes to fix the issues

  • Problem to Change(1:n): to implement a fix to the issue that is documented by the Problem

Change data between the Order, Desired System, and the Change must manage the Change lifecycle state.