Kevin:
You can go to one class, but that will not be ITIL complaint and may make matters worse.
James McKenzie
L-3 GSI
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Kevin Shaffer
Sent: Tuesday, October 31, 2006 9:43 AM
To: [email protected]
Subject: CMDB Classes
We are rolling out ITSM 7.x in 5 weeks and the last major hurdle we have in our UAT is CMDB. The feedback from our users and management is the 68 classes are too confusing and they want to simplify. I recommended getting the list to 10-15 classes, they went the extreme and said they want one class that stores everything; services, assets, documents, etc.
Has anyone gone to this extreme of just using one class. Any advantages and disadvantages, lessons learned, etc. I think it would be hard to identify all the attributes to accomodate everything in one class.
The driving force behind this is Management feels users will not relate/manage CTI's because noone will know what to classify it as ... Also reporting would be a nightmare with data in multiple forms. Management feels our Categorization is structured well enough to pull reports based on it from one form (class).
TIA
Kevin
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
