Yours truly, Charles H. Roberts, 4th Customer Service Manager (CSM) Riverside County Information Technology (RCIT) Office: 951-486-7780 Cell: 951-840-8699 eMail: crobe...@riversidecountyit.org
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Marsh, Lee Sent: Wednesday, March 24, 2010 1:06 PM To: arslist@ARSLIST.ORG Subject: Re: CI Name - Computer Systems We adopted the following naming conventions for CI's: Introduction BMC Remedy ITSM / Atrium CMDB systems have a need for unique names to use in identifying each instance of a configuration item. The convention needed to be separate from the network name so as to include configuration item that were not network addressable. It also needed to cover soft assets such as software licenses, process documents, and services. General Format: The general format for the Item name is CCC-A9999. The CCC represents a 2-3 character functional group code identify general type of configuration item. The A99999 is the format of the asset tag including a single alpha-character followed by a 5 digit number. If the item does not have or warrant an asset tag the alpha-character of "X" will be used with a 5 digit sequentially generated number. The X99999 generated number need only be unique for the CCC class of the object. Generally each instance will also have another unique identifier to associate with the item name such as serial number or license number. Also each addressable device will have attributes that capture the network device name and/or address (IP). The attributes and associated date values collected will be dependent upon the Configuration Item Class as defined in the BMC Atrium CMDB Common Data Model This is different than the functional group that is part of the name but related in that several classes may belong to a functional group. Initial Functional Group Codes: The following functional group codes will be used. CS = Computer System MON = Monitor (monitor, projector) PRT = Printer PHD = Peripheral Device or System Component (drive, scanner, digitizer, etc) DSL = Definitive SW (license) SRV = Service DOC = Document PRC = Process (document) EQP = Equipment (other office equipment, copies, bindery) BINV = Bulk (Consumables and Supplies) INV-BLD = Inventory Locations (where BLD is the Site Code) This has served us well so far in allowing us to track configuration items, primarily through asset management. If you need more details or discussion regarding some of the considerations that went into building this naming convention, please let me know. Hope this helps, Lee Marsh ************************************* Lee Marsh Remedy Administrator BAE Systems Office Automation Systems Team Antitrust Division, U.S. Department of Justice Email: lee.ma...@usdoj.gov ************************************* -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Greg Donalson Sent: Wednesday, March 24, 2010 2:58 PM To: arslist@ARSLIST.ORG Subject: CI Name - Computer Systems Hi everyone, We currently have the CMDB installed, but are not using it to its greatest potential. We are only manually imported and updating the CI's as people see fit. The initial owner of this process had the Tag Number and the CI Name as the same thing - the tag number of the CI. Nice to have duplicate data! They now would like to change the CI Name to be something more meaningful: 1. As we are on 7.0 and it shows the CI Name in the CI Viewer 2. Because virtual machines do not have tag numbers What is everyone else using as the CI Name in the Computer Systems form? Thanks! Greg _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" This email is confidential and intended solely for the use of the individual(s) to whom it is addressed. The information contained in this message may be privileged and confidential and protected from disclosure. If you are not the author's intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error please delete all copies, both electronic and printed, and contact the author immediately. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
