Use of Locations versus Use of Computer Rooms

[BalzHedinger]

Hi all

We use the Locations Table as it is designed OOB to leverage Location Data to the user in Incident Management and so on.

We populate the Locations Table from our own Active Directory and the CRM system to have this data manged automatically.

In the Locations table we use a hierarchy as follows: Country -> State -> ZIP -> City -> Street -> Floor -> Room

This is covering the Requirments for this Use Cases.

We also use the CMDB and there we have in use the CI Classes also related to geographic Informations in tables with suggested relations like:

Data Center -> Comuter Room -> Rack -> Server and so on

There we have to manage CI's wich are located in our own Data Centers but also on Customer Sites.

And in the CMDB we have also the End User Devices like Workstations.

Requirements here are detailed reports what Equipment is located where (in our own Data Centers and on Customer sites) and to have a higher Level of Detail compared to the Locations Hierarchy described above.

My Idea is to populate the table cmdb_ci_computer_rooms with data from the Locations table to become able to create the Relations in the CMDB table AND to become able to report this data using the Report engine.

Questions are:

Is this a good Idea?

Is is usefull and/or possible to do that?

Is somebody allready leverageing the locations data stored in the cmn_locations table also in the CMDB tables?

What is good practise?

Any Idea or Repliy is welcome.

regards

Balz  

[Ankush13 · Accepted solution]

Populating from location table (which already has the data) into computer rooms table is okay but also redundant. What you can have is a field in computer rooms table which points to location table (if not already present). This way, you can dot walk to location table for reporting; and you don't have to copy the same details over to another table.