Differentiate IMAC and RFC

[vjgeorgeinn]

Dear All, I am new to this forum,

I have this question for a long time, please explain the difference between IMAC and RFC.

[UKVIKING]

vjgeorgeinn

tell us what you think fall under IMAC and RFC and we will tell you whether you are wrong

... hmmm.. exam question....
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[Diarmid]

There is enough risk of confusion using jargon, but the constant use of acronyms makes it much worse.

I expect that RFC means request for change in this context, but I cannot be bothered looking up (or guessing) IMAC and so I cannot contribute here at the moment.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

[Diarmid]

vjgeorgeinn,

okay, I spotted your post at itsmfi-forum dot org. Does Robert Falkowitz' answer cover it for you?

A request for change is a document requesting a change. IMAC is, apparently a (conceptual) body of procedures designed to facilitate controlled change of computer devices. Any of these changes could be established as so-called "standard changes", but many will not.

In some organizations it may be, I get the impression, that "standard changes" do not require the generation of an RFC. I think this is mainly because, for some incomprehensible reason, people regard an RFC more as a mechanism than as a request.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718