2 Replies Latest reply on Dec 3, 2015 10:57 PM by c.reinhardt84

    How do you handle Standard Changes?

    chris1 Apprentice

      I am curious how you are handling Standard Changes. We currently have a fork in our process to handle Standard Changes themselves but I am curious how you have enabled or publish Standard Changes to users in the product.

      Do you use Standard Change Templates? How many Standard Changes do you have? Do you break Standard Changes down into different categories for easier navigation? Have you created something new to handle Standard Changes? 


      I am also curious how you handle the request to have the ability to create a standard change. Do you have something that a user submits and goes directly to the Change Manager(s)?

      I would love to have the ability for users to just take an already created changed and mark it as a proposed Standard Change. Then after some approval workflow have it published as a Standard Change.


      I was hoping to get some thoughts from others before I start working through this myself.

        • 1. Re: How do you handle Standard Changes?
          rcarins@cssdelivers.com Apprentice



          A lot of customer's I've dealt with are using the Change Templates and to make it easier to navigate use different categories as you say.


          I've always taken the approach with standard changes, because they can be considered 'Pre-Approved', they must first be raised as a Major change and go through the full change process including approvals. Once approved they could be flagged as a 'Standard Change' and from there you could simply clone the change, which then allows you have a relationship been the 'master' approved change and any subsequent standard change that are logged. This also gives you a history then of how many times that change has been implemented.




          • 2. Re: How do you handle Standard Changes?
            c.reinhardt84 Apprentice


            we have a bit of another way.

            We do change management for Enterprise Apps and so called Infrastrcuture Platforms. This platform could be "Windows Server" or "Unix Servers". We have a created a new object which is linked to the Apps and Plattform Objects. This is called Standard change templates. The object contains all the fields from the change mask. In the documentation for every platform and every app, the owner of this have to define their standard change templates. The documentation is then approved from the QA. All the standard changes they designed in their documentation are then put into the standard change object and linked to the platform or app.


            In the change module the user first has to select either the app or the platform which should been changed. If the classification standard is selected, the subject field becomes a drop down and the user can select the standard change from the list out of standard change object which are linked to the selected platform or app. Those changes are pre approved and does not need to have an approval workflow.


            This works very good for us. Good a good feedback from the community.