cmn_location table 'Managed By' group

DonD
Tera Contributor

IT operations team has a need to identify who is responsible for supporting each Location/site. We have 02 support partners providing network support for different locations.

Instead of adding a custom attribute to cmn_location table, is it possible to use "Managed by" attribute so that we create 02 different Sec. groups for each party.

Need asome advise.

1 ACCEPTED SOLUTION

From that perspective, you're right and I can tell I had similar discussion here. 

Here in the company they thought they could use the locations as CI... 

What about using Business Services and having all equipment, locations, and relationship in place for that business service?

That was my suggestion here which is being planned now.

The location table would be better to hold information like Office Manager or Facilities (if you guys use this).

 

EDIT:
Forgot to mention, we are using the Managed By and Supported By directly in the CI.

View solution in original post

4 REPLIES 4

Luiz Lucena
Mega Sage

Hi Don, 

Let me see if I understood correctly.

You have two different locations, and you want to use the Managed By Group field in the Location table (cmn_location) to populate with a security group?

If that is the case, I don't see why not.

DonD
Tera Contributor

Thanks Luiz,

My argument with the business is that Location table is merely a address book with different set of attributes.

When it comes IT infrastructure, each Location can house many items that can be supported by many teams or companies

e.g.

Network equipment supported by and/or managed ABC Prty Ltd

Servers ssupported by and/or managed PQR Prty Ltd

Printers supported by and/or managed LMN Prty Ltd

from a data management perspective, Location is a record that is owned and managed by 'Locations" CI class Owner and is not managed/supported by a single party in my case. What is installed at each Location is managed by different teams or companies.

would you agree.

 

From that perspective, you're right and I can tell I had similar discussion here. 

Here in the company they thought they could use the locations as CI... 

What about using Business Services and having all equipment, locations, and relationship in place for that business service?

That was my suggestion here which is being planned now.

The location table would be better to hold information like Office Manager or Facilities (if you guys use this).

 

EDIT:
Forgot to mention, we are using the Managed By and Supported By directly in the CI.

DonD
Tera Contributor

Thanks Luiz,

that is exactly how I intend to configure CMDB.

Each CI class will have Managed by + Managed By Group + Suported By + Supported by Group.

cmn_location table will have a CI class owner who would be accountable for the accuracy of each location record.

We also maintain Primary contact details for each location (e.g. IT support person or Facilities manager)

thanks for responding.