Is there industry wisdom, management and software tools (free preferably) for recording and tracking which users depend on what services, resources, settings and definitions centrally administered by an IT department?
My thinking is that some failures and outages can be attributed to users not being prepared/made aware of service changes they rely on.
Tracking of some things are established, e.g.: user accounts BUT other things are not, for example IP address subnets per location, environment variables, server URL addresses, locations of resources...
For example of dependency, when a user writes an application dependent on these things it can break if these are changed. The user may have to necessarily depend on these things and cannot build in contigency in the event these things are unavailable. Obviously if contigency and failover can be implemented then that is a consideration but resource to add this may be limited and there may not be favourable failover options.
Are there industry accepted processes and tools for tracking these things and making the dependents aware if they change?