That really depends on your business case. In our organization when we load CIs into CMDB one of the attributes we flag on the CI is if it is Monitored: Yes/No. And when a monitored CI is related to change tkt, upon approval of the change tkt we create an unavailability record. If the CI related is non-monitored(usually dev and qa systems) then system would not create unavailability records for them because we do not have a purpose to track their up time. So if all the 100 CIs related to change tkt are flagged as monitored, then system would create 100 unavailability records. Usually we do not have change tkt with 100 monitored CIs. Relating 100 CIs to a change tkt itself takes significant amount of time. For things like this bulk in nature we will handle them out of remedy.
On Wednesday, March 28, 2012 3:59:37 AM UTC-5, Kali Obsum wrote: > > ** > > Thanks patchsk. So for item #2, if you have 100 assets, you create 100 > unavailability records? > > > > Regards, > > *Kali Obsum* > > GS GR - Software Services | 30/F Tower 1 The Enterprise Centre | 6766 > Ayala Ave. 1226 Makati City | Philippines > ( +63 2 917 1910 | * ) [email protected] > > Shift Pattern: MNL Business Hours > Upcoming Leave or Training: None > > For urgent requests, please call ITG Service Desk (x54321) or email the > team at [email protected] > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *patchsk > *Sent:* Tuesday, March 27, 2012 2:47 AM > *To:* [email protected] > *Subject:* Re: Bulk Relate with Unavailability - ITSM 7.6.03 > > > > ** We had to do the same thing in our organization. > > 1.You could bulk relate multiple CI to change ticket out of the box. In > the CI search window search for a CI name pattern and multiple select and > click relate. It will relate all of them to change tkt. > > 2. Then we have an escalation which will create the unavailability records > on Schedule Start date of the Change tkt. > > It does some validation like if the change is approved or not. If it > is approved then it will create unavailability records once the Schedule > Start Date passes. > > 3. To extend this process, we also have integration with monitoring tools, > so upon unavailability records creation on remedy will issue commands to > turn off monitoring for the CIs.. > > 4.Once the Schedule End date passes remedy will again issue commands to > start monitoring for those CIs. > > > > There are a few checks and balances you many need to do for the process > but general idea is as described as above. > > On Monday, March 26, 2012 3:31:10 AM UTC-5, Kali Obsum wrote: > > ** > > Hi, > > > > Since it is not possible to select multiple assets and Relate them With > Unavailability in one go, has anybody implemented any work around for this? > Our process entails that for some changes, we need to bulk relate hundreds > of assets (e.g. patching). Raised this with BMC and they asked us for an > RFE. > > > > Regards, > > *Kali* > > > > NOTICE > > The information contained in this email is confidential. If you are not > the intended recipient, you must not disclose or use the information in > this email in any way. If you received it in error, please tell us > immediately by return email and delete the document. We do not guarantee > the integrity of any e-mails or attached files and are not responsible for > any changes made to them by any other person. > > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
