We have a standard change initiative whereby SOP's are typically documented as RFC's and submitted to the CAB for pre-approval. Once this is complete the SOP documentation is to be placed into a Change Template (to include Test, Install and Backout) plans for future use.
We require an RFC for any and all production changes. For things that are done in precisely the same manner on a regularly scheduled basis it is often too time consuming to have to re-create the RFC each time and/or copy an older request and resubmit it for approval. Another part of this is consistency for SOX auditors...oh how we love our SOX auditors :) -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Lisa Westerfield Sent: Friday, December 07, 2007 1:09 PM To: [email protected] Subject: Re: Non-Humor - ITSM 7 Change Templates with Work Info Regarding the templates: I have posed many questions to BMC about what can be included in a template, and to my understanding, this is one of the items that is not intended for templates. Just because I'm curious.. what kind of work logs would anyone want to add to a template? ----- Original Message ----- From: Action Request System discussion list(ARSList) _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
