3. Where Should IT Focus to Get the Most Out of CM?
When changes are clearly communicated and documented, things are less likely to fall through the cracks. Security, operations and even finance teams all have vested interests in knowing what changes are happening.
A change driven by a particular IT group might also affect security (firewalls, load balancers, IPS), networks (routing, address management), operations (backups, disaster recovery plans) and even finance, especially in a cloud-first, pay-per-use model. Making communication and documentation between groups a priority in CM delivers the biggest benefits.
4. What’s the Hardest Part of CM?
Creating a database or inventory of all your services, applications, databases, servers and networks, and how they all fit together, is especially difficult in healthcare because hospitals are full of legacy systems.
The configuration management database can’t be built overnight and takes energy and resources to update. But when a CMDB is accurate and well maintained, the payoff is enormous because many tasks and consistency checks can be automated, reducing the chance that human error will cause a service interruption.
5. What Should Teams Know to Build an Effective CM System?
Different types of changes should have different CM processes. Don’t try to make a round peg fit in a square hole: Many configuration “changes” don’t need to be approved; they just need to be documented and communicated after the fact.