Last week I wrote about the Change Management conflict checking.The example I showed was the Conflict checker ensuring that the Change is scheduled to start and finish within the Maintenance Window.I should have pointed out that this functionality is only available in the demo instance at the moment, and will hopefully be included in the upcoming October 2011 release. Sorry for any confusion there.As a reminder the conflict checker my mark a Change record as conflicted based on a few different reasons:

• The change window occurs outside of a Maintenance Window. "Not in Maintenance Window"
• The change window overlaps with another Change Record against the same component of the Infrastructure (The same Configuration Item) "CI already scheduled"
• The change occurs during a defined Blackout Window, where no changes should occur to this CI "Blackout"
• A relationship exists with a parent/child CI and the Change occurs when that CI isn't available for Change. "Parent/Child CI already scheduled In this post we are going to look at the conflict checker detecting issues where a CI has overlapping Change Windows.