It boils down to how you want to handle these types of changes for your company and do what works for you. For us, we limit the change window to a maximum of 2 weeks. If the project is scheduled to take place over several months then there would be a change for each 2 week period. Each change would ...

Old question but I wish I had a dollar for every time this question was asked.

The elves are back at 100% production here as well. For us it's not just the lack of support, it's our biggest money making time of year so any hit to our production systems is completely unacceptable this time of year. I wish you all a great and successful New Year and may the auditors be kind! Sandy

Merry Change Freeze To One And All

John, you should write a book on Change Management,. I'd but it!

For us an RFC is required. If a change is being made to production then an RFC is required. Just because that works for us doesn't mean that's the best policy for you. Here incidents are used to log production issues, RFC's are used for production changes. Sometimes 1 is related to the other and are...

For us ANY change to a production environment requires an RFC, in this case it would be a standard change. The benefit of using changes for these types of hardware replacements is now you can run a report and identify possible weak models of certain hardware to avoid in the future.

"Furthermore, if we take an example of a Change Request and look at the numbers, more inefficiencies can be found. For example, if we have 50 Change Managers/ Approvers on a request, yet only one Approval is required for the change to take place. 1 Change Manager approves this change relatively quic...

Identify need for change - Create/submit change - Change control review - Approval - Implementation - Post implementation review.

Up to you to decide how you want to handle Retro, Routine, Normal, Expedited and Emergency changes based on your needs.

Cabs scheduled as per your requirements above.

Google & Itil Foundation course.

"Don't those guys realize things need to get done?"

Here's what I use: The objectives of the Change Management process are to: o Ensure that changes are made with minimum disruption to the services IT has committed to its users. o Support the efficient and prompt handling of all changes. o Provide accurate and timely information about all changes. o ...

My favourite reply to my Fast Pathers (We use Fast Path here) is "Poor planning on your part does not constitute an emergency on mine".

Some people just never learn though...

"Planned" is that some new ITIL term going around? Sounds like it could be useful.

We're using Remedy for our Service Desk (Incident Management), Change Control and customized for ITSR's (Software, access req etc). Unfortunately the decision was made to switch to Assyst without any consultation with the Change Management team. I've tried searching for reviews of Assyst online and ...