For example, it often makes more sense to keep financial data in an IT financial management ITFM tool and software license information with a software asset management SAM tool.
The data can be imported and mirrored in your CMDB, even without that being its primary storage space. Many organizations struggle to develop and maintain an accurate CMDB.
The most common issues are discovery tools running too infrequently, an absence of automation rules, or a reliance on manual inputs. The typical answer to these challenges is event-driven discovery that augments traditional, bottom-up discovery.
For those unfamiliar with those terms, bottom-up discovery is when assets are mapped starting with infrastructure and branching out into customer-facing CIs. Event-driven discovery is when something happens—an event within a system, a problem, etc. Then, based on that event, the system maps the related CIs and their connections. Now, not every CI is discoverable. For example, your team may want to map monitors in your CMDB.
The key to accuracy is harnessing the power of both bottom-up discovery and event-driven discovery to get the clearest picture of your assets and their connections. There is a perception in some organizations that CMDBs are for modeling legacy infrastructure and software, rather than the new stack of cloud and software-defined infrastructure and the modern workflows hosted on them.
Choosing the right tool is paramount if you want to avoid the unhappy failure statistics above. Some CMDB tools amount to little more than asset repositories—data structures fixed on legacy physical infrastructure and discovery tools that react slowly to any changes.
To succeed with a CMDB, you need one that accounts for new types of assets and is capable of quick change. In general, it makes sense to start high-level and get the services right and then only go wider or deeper where needed to meet your organizational goals. Technical entities include business services, technical services, applications, software, databases, containers, virtual machines, operating systems, hardware, networks, ports, etc.
Non-technical entities can also be modeled in your CMDB if you need to represent them as either dependent or impacted by other assets in your IT service mapping. Non-technical entities may include users, customers, organizations, locations, service agreements, documents, etc. Lastly, cloud services should be taken into consideration in the design of a CMDB model. Both SaaS offerings e. Google apps, Dropbox, Salesforce, etc. In ITSM, incident management decreases time to resolution and minimizes business disruption.
Author : Stephen P. Author : J. This book presents a comprehensive survey of the Vesta system for software configuration management SCM. Author : Steve J. Sign In. Standards Store. Purchase History. Currency display settings. Manage society memberships. Featured Products. View All Publishers.
Quality Management. SCC Standards Store. Popular Standards Bundles. Drawing and Drafting. Telecommunications Standards. AWS D1. Means, Inc. It describes a Plan for managing both software development and maintenance of a commercial product line.
Some of the different characteristics illustrated are shown in Table 1. Article :. DOI: Need Help?
0コメント