Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: JeremyLach8667
New Today: 20
New Yesterday: 36
Overall: 190212

People Online:
Visitors: 82
Members: 0
Total: 82

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - How is a change window determined for an event?
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

How is a change window determined for an event?

 
Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message
cjb83
Newbie
Newbie


Joined: Nov 19, 2014
Posts: 1

PostPosted: Thu Nov 20, 2014 7:02 am    Post subject: How is a change window determined for an event? Reply with quote

We are in the process of putting together a procedural definition of event 'change windows' in order to narrow down the windows scheduled for our changes.

Typically, are windows determined by the length of time needed for just the change itself and service verification/backout period? Or is there usually an additional monitoring period included as well?
Back to top
View user's profile
estaclaut
Newbie
Newbie


Joined: Apr 13, 2015
Posts: 11

PostPosted: Mon May 04, 2015 9:43 am    Post subject: Reply with quote

The 'testing' phase of a change implementation could include an activity of monitoring also.

It depends on what the change policy views as monitoring?

If the monitoring period extends over a matter of days, weeks etc...then that's a bit of a stretch to include in the window.

Perhaps the monitoring phase is performed under operational activities for a set period?

ie: the change windows is 5 hours. Once the change window is complete and the change is in operations, then the 'monitoring' is just performed as an operational task and any events that are triggered are managed accordingly.
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3493
Location: London, UK

PostPosted: Sun May 17, 2015 9:26 pm    Post subject: Reply with quote

Think it through

the change window should be the total time for the implementation and roll back of the change. Nothing more. Nothing less.

If the change requires a week of burn in, then, to be honest, you will have two change windows - one for doing the work and one for undoing the work

Of course, this depends - as estaclaut states - on your change mgmt. policy and operational restrictions
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
arun121
Newbie
Newbie


Joined: Mar 03, 2016
Posts: 6

PostPosted: Wed Mar 09, 2016 10:24 pm    Post subject: Reply with quote

I think,

First We should need to process of putting together a procedural definition of event change windows in order to narrow down the windows scheduled for our changes.
Back to top
View user's profile Visit poster's website
JScratch
Newbie
Newbie


Joined: Sep 06, 2016
Posts: 12
Location: Minnesota

PostPosted: Wed Sep 07, 2016 4:22 am    Post subject: Reply with quote

I like UKVIKING view point.

rule of thumb for our change activity is all changes have a warranty period. If a change went in but for some reason functioned for an entire 3 weeks before an issue was found we still would go back and mark it as creating an incident or introducing a bug.

If the monitoring period needs to be captured it should be called out in the change order, if for anything it would be auditing purposes (if you are subject to auditing).

If you go to the level of creating tasks under the change order or release record the tasks time frame should reflect the ACTUAL implementation or activity (not the entire window plus monitoring) and if you really wanted, create an additional task for awareness around the monitoring period.

lots of ways to do this based on your companies level of detail you choose to capture.
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Change Management All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.