When to create a new CI class?

[gaidem]

As we are on boarding more and more CI's, the question keeps coming up if new CI classes should get built. This may seem like a simple question at first; Linux Server = Linux Class, Windows Server = Windows Class.

When you get more into the details things aren't so clear. For example, out of the box there's network gear. Items like switches, routers etc. are withing this class with a flag to determine the specific use.

Also, if you think about it, there's really no technical driver for this decision. Everything from transform maps, modules, views. security, reporting etc. can be accomplished without a new class getting created.

My question for the audience is more on the business side. I'm wondering if anyone has had similar challenges and/or has setup a guideline for creating a new class.

Again, my question may seem simple, but I'm just sanity checking with the larger group.

Thanks

Matt

[DrewW]

I do it when I would like a clear data separation because of fields. Like when we needed to add Medical Equipment to the database. Med Equip has special field needs and those fields are only needed for Medical Equipment. So new class.

[camran]

I will suggest, during data modeling (classes should be designed). Though we can create new classes anytime it's not a best practice.

In any case, you have to be very clear, what you want to achieve. I personally like close to be OOB.

You have to ask a few questions if you need new class, why you need it ? For reporting purpose? Assessment purpose?

In simple cases, both can be achieved by using the existing OOB classes. If there is any other purpose let me know and I will happy to help.

Regards

Camran