One common reason for introducing an NCCM tool is for performing bulk changes against multiple devices. This runs a close second to the need for device configuration management.
So, what exactly do users want to change? The most common answer to this question is login authentication information. In other words, changing the username or password that is required when they login to network devices. Like the personal identification number for a credit card, it is not recommended to use the same password for network devices for a long time. Depending on the compliance requirements, it is now common for some organizations to be required to perform a regular bulk change every quarter or six months.
The operators of typical networks are managing many tasks with limited human resources. Even if it is once every few months, just executing the change will be hard for them against so many devices. There may need to configure a different password not just by location, but for each of the thousands of devices. Despite their best intentions, I often heard they cannot keep up with the requirements.
It might sound like a good idea to integrate the logins at network devices into an authentication system like a RADIUS server. However, since there is a high risk of fraudulent use of IDs, I feel there is a need for secure password management in the local network device side too.