Using OOB to identify changes by region

[califiniyal]

hello

The OOB ServiceNow team is removing customized region fields (NA/EMEA/APAC/LATAM) in order to adhere to OOB ServiceNow standardization. I'm trying to understand if there is a standard way to identify Changes based on region. There is no standard way companies identify Changes based on region using ServiceNow, and I have not been able to find any information on this.

[Mark Manders]

OOB ServiceNow does not add 'region' to a Change. This is because regions can be defined in very many ways (globally Europe, Asia, etc can be seen as regions, but locally, it could be states, or even counties). 

The answer to your question completely comes down to how you define a change by region? Is it related to the team performing the change? Is it related to the localization of the object that is changed (and how to handle a change that is company wide for a global company)? 
You will need some reference to your region on the group, the user, the CI, or whatever you are changing. Only then it's possible to define it for a change and report on it.

Example: if it is a change on the wifi network of a Los Angeles office, the CI is in some way set to the location of that office and you can use that to define the region. Still: you need to have Los Angeles defined (in some way) as part of a region.

Go to the ServiceNow team and ask them this question. Because if it is a company requirement to report on region, they will have to provide a way of adding some way of recognizing it, even if it's just a field on the location form stating the region of a certain location.
Ask them what their reason is to get rid of customization that is important to the company, if it isn't replaced with something that does the same, but then OOB. I am all for OOB, but not if requirements can't be met by the OOB system. Customization like this (a field) is of no risk and won't break anything on upgrades.