RFC Form

[jonbigsky]

I am looking for an example of what an RFC (Request for Change) form should look like. I am currently using one that is cumbersome and data redundant. It seems as though this form has been manipulated a number of times by several different folks.

Does anyone out there have an example of one that they could share?

Thank you.

[Ziad]

Here's the one we're currently using.

- Implementation
<Implementation steps here.>

- Verification
<Verification steps here.>

- Fallback Plan
<Fallback plan here.>

- Dependencies
What alerts / monitoring points need to be deactivated during CMR execution?
Is there a need to update any drawings?
Change any labels on cables, racks etc?
Update any procedures?
Update any monitoring systems?
Update any other documentation?
Who needs to be informed about the change?
Do we need to inform customers?
Inform facility management, security agents or any vendors?
Request any maintenance window?


Regards,
Z!

[Fabien]

I don't have one to share but a few things I'd like to add to the previous post:

Description of the change
Who is the requester?
Business reason, Business Case
Costs (hardward, software, people, accomodations, ...)
Who approves the investment/spending?
Risk Assessment
Schedule, window of opportunity

... you need to design it in a way that makes sense for your organization and for the type of changes that you have decided to control obviously.

You also need to define what is mandatory, who may be working on adding some information at a later stage etc.

Hope it helps...
_________________
BR,
Fabien Papleux

Accenture
Technology Consulting | Service Excellence
Red Badge Certified

Twitter @itilgeek

[fighter]

Let me know your email.

I might have something for you..

Cheers

Vimzie!!

[Ed]

I operate a paper Change Management system, and am happy to share my RFC/Flowchart/Release Document/procedures with anyone who is interested.

However, I am about to go into hospital to have a sliiped disc repaired.

Please bear with any delays that may occur.

my e-mail address is

edward <dot>wadey<at>yahoo<dot>co<dot>uk.

I am a Change Manager with in excess of 30 years experience that I am more than happy to share

Regards

Ed

[fighter]

Ed

Get well soon!

Cheers

Vimzie!

[Ed]

Thanks Vimzie - Much appreciated - however, I am going senile My E-Mail is edward<underscore>etc not <dot>

Regards

Ed

[jonbigsky]

Thank you all for the suggestions! My email address is jonbigsky@2below.com. Please drop me a line if you have other suggestions or example documents.

I am really looking forward to streamlining my process for Change Management in the coming weeks/months.

Thanks again.

[fighter]

Jon,

I have sent you the form. let me know if you have any questions.

Cheers,

Vimzie

[eisbergsk]

2 cents from a Problem Gal- Jon, I'm not sure what is on the paper forms you've been sent, but I really like to see a link (name, description, subtle hint - I'll take anything) to the Configuration Item that is being Changed.

(interesting point - I focus on 'BIG DEAL' incidents for Problem mgmt, and these are RARELY the result of change. no lie! I just did an analysis for our internal auditor. Having the CI on the Change helped disprove that assumption.)

Ed, did you have the doctor file the appropriate change control forms for your operation? especially the recovery portion.... *grin* get well soon!
/Sharon

[Ed]

Hi Sharon - sadly he did better than that - he decided the risks were too great and cancelled the op -


no seriously only for a couple of weeks

But looking at Jons problem , he probably has not got a CMDB if he is thinking of using a paper system - this is why we have no mention of CIs in our paper RFCs

I do agree that most changes do not cause problems - our stats show that over 97% of changes go off smoothly

Regards

Ed