4 Replies Latest reply: Feb 7, 2012 12:28 AM by vinayak NameToUpdate RSS

Change Timing vs. Standard Change (ITIL)

TKopacek@bmcdn

Which Change Timing selection compares to the ITIL Definition of a "Standard" Change. My customer is thinking that Standard Change in ITIL not compares with "Normal", but the BMC documentation says "Normal" Change is equal Standard Change.

Can somebody clarify this point?

  • 1. Re: Change Timing vs. Standard Change (ITIL)
    DaveEhm

    We consider normal to be a standard change, since it's OOTB behavior follows the required status and approval steps displayed starting page 367 of the BMC Remedy Change Management 7.0 User's Guide.

     

    Hope that helps.

  • 2. Re: Change Timing vs. Standard Change (ITIL)
    Sydney Dent

    I would consider the timing "No Impact" to be the closest match to a "Standard Change" in the ITIL sense. A Standard Change, according to ITIL, is a change that is "preapproved" because its impact is well understood or very limited. There is an excellent white paper on working with Change Management Approvals that I have referenced here.

     

    http://communities.bmc.com/communities/docs/DOC-2727

     

    I think the section you will want to look at is building Change Management Approval Processes. There is a section on "by passing" approval processes. In this case, you could build an approval process that will by pass all but one or two approval processes.

     

    Regards,

    Syd

  • 3. Re: Change Timing vs. Standard Change (ITIL)
    Steve Wilson

    Per the Product Manager…

     

     

    Standard - A type of change that must be coordinated by a change coordinator and for which a change template exists that has been approved by the service owner. Standard changes are considered changes to the infrastructure that follow an established path, is relatively common, and is the accepted solution to a specific requirement or set of requirements.

     

     

  • 4. Re: Change Timing vs. Standard Change (ITIL)
    vinayak NameToUpdate

    ITIL and BMC's Standard change Definition:

    ITIL:An ITIL standard change quite simply refers to pre-approved changes.

     

    ITIL Pre-approved changes can be defined for a variety of tasks,but they will typically be low risk, low effort changes that have a low o rknown cost.

     

    BMC:Standard indicates a change (for example, a computer upgrade) that is

    typically pre-approved and requires only approval by the change manager.

    Standard changes follow the out-of-box change process defined as per ITIL

    specifications.

     

     

     

     

    ITIL and BMC's Normal change Definition:

    ITIL:An ITIL normal change refers to changes that must follow the complete change management process.

    By definition a normal change will proceed through all stepsof the change management process and will eventually be reviewed by the ChangeAdvisory Board (CAB).

     

     

     

    BMC:Normal indicates a standard change (for example, the creation of a virtual

    machine with standard specifications) that is typically pre-approved and

    requires only approval by the change manager. Normal changes do not

    follow the standard out of the box change process. The default value is Normal.

     

    The only difference not qualifying ITIL's Standard change with BMC's Normal change is that

    Normal changes do not follow the standard out of the box change process while Standard does.

    But BMC do consider them on equal basis as you said.

     

    May be your customer is relating to that?


    Hope so this clarifies you somewhat!