Page 1 of 1

Change Management Process

Posted: Wed Apr 12, 2017 3:50 am
by Subhendu
Hi all,

I am new to this forum. Can anybody tell me,

If a server is in Build state, should there be any incident raised for any issue foubd in it ?
How do I get a change done for this server which is not in production and replacement of any part is involved ?

Posted: Wed Apr 12, 2017 2:53 pm
by UKVIKING
No.
You don't. It is a build so it is not a change

Posted: Wed Apr 12, 2017 3:09 pm
by Subhendu
Thanks john for the response.

So , just to clarify,

No incident number for this.
And ,
No change number for this.

Right ?

Posted: Thu Apr 13, 2017 2:29 am
by UKVIKING
Subhendu,

Since the device is not in operations - an incident is not usually called for. as Incident tickets are for service impacting events.

Now that would depend on the build request process and of course the ticket system usage within your organisation.

If the incident management policy states that build and non operational errors and faults go through the system, then my assertion is incorrect.

As for change mgmt; it is usually associated with operational related changes .. ie changes to production,

So if there is a supporting process (project or build related ) about broken build systems, then that should be used.

whether it is a f formal ticket .. it depends

Posted: Thu Apr 13, 2017 4:30 am
by Subhendu
This makes more clarity now. I really appeciate for tking your time to address my voncetm