Hi Alex, the CMDB is the Database of the CI. BMC Asset Management expands the attributes on the CMDB to manage the complete lifecycle of an IT Asset. But it address also things like Ordering and Purchasing of IT Assets, Software License Management and others. The CMDB is only an instrument to hold the data for Asset Management.
Thomas is 80% correct, err complete. He states, quite correctly that the CMDB is the data store for Asset Management. What is not stated is that because the CMDB is the repositor for Asset, is is possible, probably even, that you will have Assets in the CMDB which are not CI's.
For example; If you will recall the discussion we had on monitors being a CI or not. We established that while a 19" flat screen might not rise to the level of a CI, a 64" might. However, it might just as well be said that no monitor will be managed as a CI, regardless of size or cost. This is because while you might record the smaller flat screens as bulk inventory items (via Asset Management), you would probably want to track those 64" Super Bowl Party viewers individually because of the cost associated with them. Ergo, you create an Asset Record via Asset Management (using BMC_Monitor). However, if you are not required to open a change or incident request against it, it is not a CI.
Not all Assets are CI's and not all CI's are Assets.
An expensive oak desk for your CIO might be an asset, but it isn't a CI. A Logical Business Service which underpins a Service Offering in your Service Catalog is a CI (you most certainly had better be managing it via Change and Incident) but it has no intrinsic value so is not an Asset.
In the BMC ITSM world, we are splitting hairs, I agree, but the bottom line is - what do you manage and how do you manage it? Answer that and you'll know if it is 'fish' or 'foul' or neither.
Does that help?
Thanks. I think I'm getting there but still confused....
Then let me ask you this.
I have 64" Sony monitor as CI.
From BMC's "Mapping your Data to BMC Atrium CMDB Classes" pdf file,
I got CI - monitor
Class - BMC.CORE:BMC_Monitor
Tier 1 - hardware
Tier 2 - Peripheral
Tier 3 - Monitor
CI Type in BMC Asset management - System Component > Monitor
So what do I do now with this in CMDB and Asset management.
I would greatly appreciate if explained in steps to put this in to both CMDB and Asset management.
once I grasp this, I can work on all the other CIs
Thanks and sorry if it's rudimentary question.
Are we talking two different AR Systems here, or one where you have entered the same CI in two different ways?
I think I understand what is going on - it's one AR System. In Asset, when you create a new CI you would click "Manage CI's", "System Component/Monitor", "Create"... This is just a menu construct. Once you have the form open, you have the categorization fields on the "General" tab toward the bottom left of the form. Here is where you put the categorization we discussed.
No problem - doing this via blog post isn't always straight forward.
So, think of Asset Management as the interface where you will do most of your manual CI creation as well as Life Cycle Management of CI's.
Use Atrium Core for creating relationships like Dependency, MemberOfCollection, Component, etc. You CAN create CI's using Atrium Explorer but I find it easier to do so in Asset.
Once you have created your monitor and the computer system (laptop?) using the Asset interface, open Atrium Core/Atrium Explorer. Click on the "Find" bar in the navigator at left and expand the "Quick Find" option. Enter the CI Name you gave for each, one at a time and perform a search. You can drag each one into the BMC.ASSET view which opens by default. Once you have both of them present in the view, click the button just left of the relationships option dropdown. Select Component/HostedSystemComponent and draw a line from the laptop to the monitor.
This is the typical use case for Explorer. The CI you modify in Atrium Core is the same CI you created in Asset - or should be.
You might try attaching some screen shots if I'm not getting your use case right.
Thanks a million. That did clear up a lot.
currently, data is in external database so probably need to use discovery tool to get CIs
because there're more than 10000 of them ranging from monitor to switch (I can't see myself doing that all manually)
By the way, do you have template you use for meeting with stakeholders.
Will be having a kickoff meeting but not sure what I should bring to the table.
Alex, have you look at the CMDB docs and the Asset Mgmt docs? There's a CMDB modeling guide, for example, that may help you in how to model your systems. A dell server would be in the computer system class; you can look at the attributes in that class (the CDM model diagram will help here)
When you install Asset Mgmt, there are a few attributes added (currently) to the CMDB; think those are in one of the asset mgmt guides. But Asset Mgmt mainly adds things like contracts, cost fields, outage windows, etc. the CMDB is really the CI attribute place.
There isn't any real difference between the two, Alex.
The CMDB is the database, Asset Management is the application which consumes the data in the database. There aren't two different databases, there are two types of forms, or views, which are used to view, create & update data. CMDB forms (BMC_Core:BMC_ComputerSystem) and Asset Forms (AST:BMC_ComputerSystem).
For the most part, you will find little difference between the two forms as they are just different 'views' of the same data, at least for the standard CI Attribute data. What you will see in Asset which you will not see in the CMDB forms is the data which is specific to Asset Management. e.g. Financials Data.
Does this help?
No, you should put all imported data into an import dataset. Never import directly into BMC.ASSET. This is your ‘Gold’ copy for your data. It should always reflect what is true about your environment. It is the source you will send auditors when they have questions.
When you import into an import dataset, e.g. MS.IMPORT.SCCM, you will run reconciliation for that dataset against BMC.ASSET. Reconciliation will migrate over any changed attributes.
Asset Management, by default, uses BMC.ASSET as its primary data store.
Curtis A. Rowell, Sr. | Senior. Consultant
ITIL v2 IPRC Practitioner | Remedy Advanced Core Solutions Certified
office - 703-812-0156 | cell - 571-234-3430