Congratulations, you have an IPAM solution! But don't that lull you into a false sense of security.
As a parallel, one of the problems I've seen with people doing BC/DR implementations is that a lot of effort is put into Disaster Recovery, but the Business Continuity bit gets forgotten. In some ways IPAM is vulnerable to the same kind of wonky thinking. The IPAM system itself may be awesome, but unless it becomes a central part of all your processes, it's just another out of date tool sitting on the sidelines. Involving the IPAM solution in all Moves, Adds, Changes and Deletes (MACD) is critical to maintain data integrity and accuracy.
It's much easier to ensure your IPAM tool is maintained if there's one team managing all things IP, but when you have different teams running IP allocations, DNS and DHCP, it can be a whole lot more difficult. It must be done, though, or your IPAM tool will start being ignored because it's not always "right" when you check against reality. Management have to support this too, and will need to agree to come down hard on anybody willfully bypassing the IPAM tool and potentially causing conflicts.
Think about it - what is the true cost of going back and changing an IP allocation after the fact, because somebody picked their own IP and ignored the IPAM tool? Whether you're using IPAM software, Excel, or a piece of paper, having that tool engaged in every process is critical. Can you afford not to?
I'm curious; how successfully have you managed to keep IP Address Management in your processes? Do you still get conflicts caused by rogues bypassing the processes, or problems caused by teams managing DNS or DHCP?
