David:
I think that you now understand what I was trying to get at. If you have a homogeneous environment, you can use one and only one class. Otherwise you should use only those classes you need. No Java programs, no need for J2SEE classes. No database server, no need for those pesky database classes. However, if you have these, then you should use the appropriate classes.
And each CMDB 'solution' has its own 'best practice' classes. Sooner or later, the number of CMDB 'solutions' will come down in number. Until then, you are 'stuck' creating your own custom 'solution'. The trick is to get as close as your actual system setup is from an out-of-the-box 'solution'.
James McKenzie
L-3 GSI
________________________________
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of David Sanders
Sent: Tuesday, October 31, 2006 1:43 PM
To: [email protected]
Subject: Re: CMDB Classes
**
James
There are about 40 ITIL certified toolsets on the market, each of which will have its own CMDB which is ITIL certified and based on 'ITIL best practices'. They will all have very different structures. Remedy's Atrium CMDB is not THE CMDB, it is an example of a CMDB - there are many others, and some of them will be better, and certainly easier to manage.
What level of detail needs to be stored for CI records depends upon the organization's requirements - the only requirement from an ITIL perspective is that the CI record identifies the infrastructure element uniquely. For some organizations that might be 10 attributes in a single table/'class', for others it might be 100s of differing attributes in many tables or even in several federated databases.
David Sanders
Remedy Solution Architect
Enterprise Service Suite @ Work - ITIL-certified toolset
==========================
ARS List Award Winner 2005
Best 3rd party Remedy Application
tel +44 1494 468980
mobile +44 7710 377761
email [EMAIL PROTECTED]
web http://www.westoverconsulting.co.uk <http://www.westoverconsulting.co.uk/>
________________________________
__20060125_______________________This posting was submitted with HTML in it___
