Enterprise CMDB The Enterprise Configuration Management Database (ECMDB) is targeted toward businesses that want to monitor, manage, measure, track, alert on change, and generally understand business systems that consist of a large number of components, business, and support personnel. For example, a bond trading service may have multiple application, and web servers, several databases, Linux, UNIX, and Windows servers. There will be security products, network storage, disaster recovery procedures and hardware, etc. that are necessary for the service to operate properly. The ECMDB makes it easy to either manually enter the relationships or have them populated automatically by discovery tools. In addition to the hardware, software, network, database, and storage areas, it is beneficial to know which individuals or groups are responsible for the service from both a business perspective as well as an IT perspective. Who are the line of business users and managers? Who starts and stops the application or its components? Who monitors the log files? Who is in charge of backup and restore, business continuity, and disaster recovery? CMDB relationships The ECMDB lets you easily track all relationships by relationship type. The Enterprise CMDB extends the capabilities of the ServiceNow platform CMDB in the following areas. Extended configuration item types Clusters Database Instances (Oracle, MySQL, MSFT SQL Server) File Systems (Direct and network attached) Linux Servers Solaris Servers AIX Servers Extended relationships Accurate description of relationships between items, and between items and people or groups, is important to understand the fabric of a business service. ECMDB provides many relationship types out of the box, but it is easy to extend the number of relationship types. Example relationship types include the following. Connects to Depends on / Provides Service to Powered by / Powers Protected by / Protects Disaster Recovery Provided by / Provides Disaster Recovery for Visualization The system can show relationships as a hierarchy using a standard treeview, flattened, or graphically, all in a simple web interface. Auditing Auditing of changes to configuration items is turned on by default. Federation Federation of third party discovery and configuration data is supported through standard synchronization offerings (SMS, LAN Desk, others) and through the CMDB Discovery [cmdb_discovery] table. Configuration item modeling (product models) Model driven configuration management allows the definition of CI models up front that can be associated to product maintenance lifecycles, cost centers, and support organizations, as well as provides a means for capacity and inventory planning. By defining models for CIs (which have a many to one relationship to the model), you can dynamically group actual discovered or imported CIs into logical, operational, and financial models. This facilitates an organized approach to managing your assets (CIs) in their respective domains. Business service tables In the CMDB, the Business Service table [cmdb_ci_service] stores information about business services. A business service is work or goods that are supported by an IT infrastructure. For example, delivering email service to an employee can require services such as email servers, web servers, and the work to configure the user's account. A business service management map graphically displays the configuration items (CI) that support a business service and the relationships between the configuration items. The Business Service table [cmdb_ci_service] stores the business services in the CMDB. Table 1. The Business Service table Field Description Number Automatically generated unique identification for a new business service record. Its value consists of a 'BSN' string and a unique number. This identification can be referenced by other forms and scripts. The Number field is visible with the Service Portfolio form view.Note: The Number field in business service records that were created before the field was added, is null. Business criticality The importance of this service to the business. This field can be used to determine disaster recovery strategies for this service. Default options are: 1 - most critical 2 - somewhat critical 3 - less critical 4 - not critical SLA A reference to the Agreement [sla] table. Service classification Designates the type of the service. Business Service (For more information, see Business Services) Technical Service (For more information, see Create a technical service) Service Offering (For more information, see Service Offerings) Shared Service (For more information, see IT shared services) Application Service (To represent a service that is classified as a business application) Billable Service (To represents a service that is billed, or that is cost managed) Used for Designates how this service is used. Default options are: Production Staging QA Test Development Demonstration Training Disaster Recovery Users supported The users that this service supports. A reference to the Group [sys_users_group] table. Version Use this field for your own versioning processes. The Service Configuration Item Association table The Service Configuration Item Association table [svc_ci_assoc] binds a business service and a configuration item (CI) to track which CIs are part of each business service. Table 2. The Service Configuration Item Association table Field Description Configuration Item Id A reference to the configuration item [cmdb_ci] table. Service Id A reference to the business service [cmdb_ci_service] table. The Service Relationship Association table The Service Relationship Association table [svc_rel_assoc] binds a business service and a relationship to track which relationships are part of a business service. Table 3. The Service Relationship Association table Field Description Relation Id A reference to the CI Relationship [cmdb_rel_ci] table. Service Id A reference to the Business Service [cmdb_ci_service] table.