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.
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.
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