Do you have a good way to manage location data?

[Tobias]

Hi, 

How do you manage your location data, so it is kept up to date? 

We have an agent on servers and PC's populating various classes and attributes in servicenow - location table one of them. Previously this agent was fed with a list of locations based on IP-ranges, so servers, based on their IP-address, were given a location value. This is however outdated and tedious to maintain - thus I'm looking for inspiration for other ways. 

/Tobias 

[Rutger]

I would suggest creating an integration like a scheduled import with/from an IP management system (assuming it is populated with location data), to be found in for example the network support group, or else perhaps one with/from a DC database system like Nlyte, which is populated with data center parameters like geolocation, rack location, power characteristics? 

[CMDB Whisperer]

It really depends on how granular your locations need to be and what sources of truth you have for that data, but most likely you have sources of record that you can use to define your location data in ServiceNow.  Some suggestions include:

• Corporate real estate databases, building plans, etc.
• Network locations for datacenters, sites, buildings, etc.
• Existing fixed asset registers

This may require some up front data cleansing and normalization, and it is strongly recommended that naming conventions and unique codes/IDs are established which can be used to reference locations across any system so that synchronization can be maintained through integrations with those systems.

[alandust]

Yokohama introduced an IRE Support for non-CMDB tables. This would be worth taking a look at.

https://www.servicenow.com/docs/bundle/yokohama-servicenow-platform/page/product/configuration-manag...