Something that will be an issue for you is both complexity and the fact that you can configure the system quite a bit. If you have enough time to demonstrate all of the applications, you should start with two Incidents on the same issue, which then you relate to a Problem ticket, which produces a Known Error. Then you create a Change Request to address the Problem ticket. If you need to fit Asset Management into the picture, you could create the Incidents for a specific asset, then have the Change Request modify that asset.
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Zoltán Nemes Sent: Tuesday, April 08, 2008 10:23 AM To: [email protected] Subject: ITSM7 scenarios ** Dear Listers! We have recently got to install the ITSM7 package and begun discovering it. I know that a lot of you are dealing with ITSM7 and probably faced the same questions at the beginning. We were asked to create simple and straightforward scenarios, which could be used by our sales guys in their presentations to the customers. If any of you have such scenarios or any useful documentation and are willing to share with me, I would be very grateful. Thanks, Zoltán Nemes Remedy Consultant iSEC-IT, Budapest, Hungary ________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access <http://us.rd.yahoo.com/evt=47523/*http:/tc.deals.yahoo.com/tc/blockbuster/text5.com> , No Cost. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
