I won't do that. It's a double edged sword. I've had my management tell me to make something a SEV1, I *think* mostly because it's important to them, or maybe impatience.
My stock answer is always, if it's a SEV1, I have to do anything to resolve it, up to and including disrupting the system further. A true SEV1 in my book is something of a crippling nature, that you work around the clock on until fixed or a workaround is in place, at which time, the problem is no longer a SEV1. If I expect my vendors to work around the clock, then I better be prepared to as well, otherwise it is not a SEV1. Making it a SEV1 just to get priority response is bad form, and tends to get ignored in the future by the same vendors. _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
