Hi Alec, Hope things are going well for you! Per your questions below: #1 I know this is reminiscent of our discussions way back when, but this item comes down to 3 things: process, process and process. Wrapping CMDB governance with Change Management is the single best way to keep track of those types of minor changes. There may be ways to coerce some of the information from Radia or other discovery tools (like cross-referencing a general location to an IP subnet), but for things like changes in ownership, installed location, if the CI goes off the network (to Inventory or Obsolescence/Disposal, for example), etc. it's pretty much manual in terms of managing the data. Now, that being said, there's always the potential for building Workflow and application logic which would update a CI from a Change Request, but this assumes proper system usage - i.e., the CI is related properly and there's sufficient and accurate data in the CRQ. As you well know, the chances of that tend to be not that good as even the most disciplined users sometimes provide incomplete data and it would have to be built around very specific use cases as well, so that would limit the scope of what could be updated in the CI. Not to mention, this begins the drift away from out of the box which can cause problems with upgrades. So, your best bet for some organization around those types of changes is to enforce use of the Change Management process to make sure there's at least some record of the change and then include a review of these changes in your Audit Policies to catch the CI's which weren't updated by Implementors of the CRQ's. #2 If you have some sort of key field between your HW and installed SW for each piece of HW, you can use this to create appropriate relationships in your CMDB. Depending on how you're integrating with Radia, you'd create an instance of BMC_Software (or a derived Class that's more suitable) for each installed instance of software. Then, for each installed software instance, you'd also create an instance of BMC_HostedSystemComponents to create the relationship between your hardware CI and the installed software CI's. The actual mechanism to do this varies with integration method - for example, if you're using the Atrium Integration Engine there's an option to define mappings for Relationship Keys and their associated Classes so the relationships are created during data import. Other integration methods would have differing ways of accomplishing this either by building workflow to process CI's as they are imported or by creating separate import files if you're creating CI's manually from spreadsheets and such. If you can provide more specific information on your integration mechanism, we can probably provide a lot more direction on how to get it done. Hope this helps! Chris Woyton
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Alec Murchie Sent: Thursday, May 08, 2008 1:07 AM To: [email protected] Subject: Minor CI changes & SW instances in R7 ** Folks, I've 2 quite different issues I'd like some advice on: 1. Minor changes made to CIs? eg. when a PC asset changes Status or location how do you ensure that they go thru' a minimal Change Request (ITIL) process. Is there an automated method within the Remedy suite? 2. Software instances in Remedy Asset Management - we have started with hw assets (Laptops/desktops, servers) but now want to include the sw that runs on each of them (applications). What's the best way to achieve that if you already have Radia detecting/storing sw. BMC Remedy User Version 7.0.01 Patch 002 Using Change, Incident, Problem and Asset. Appreciate the support, Alec Alec A. Murchie Manager CMDB / Asset Management Process Support Group Phone: +44 1764 655190 Cell: +44 7717 346035 CONFIDENTIAL & PRIVILEGED COMMUNICATION The information contained in this message is privileged, confidential, and protected from disclosure. This message is intended for the individual or entity addressed herein. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The sender totally disclaims, and will not accept, any responsibility or liability for the unauthorized use, or the consequences of any unauthorized use, of this communication or message. Thank you __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
