Blueprint template | Default Data Domain | Description | Updated in version |
---|
PDMC - Business Processes | Business Processes | Justin | The Practical Data Model for CMDB | v1.0 | L2 - Business Processes. Considerations regarding this data model: - Note that "Business Service" or "Service" class in ServiceNow has many use cases. Multiple logical classes in the PDMC are using the Business Service class. - Are all the different "services" in scope: business services, service products, service packages, customer facing service and backend services. - Role of the Business Process can vary based on requirements and overall data scope | 1.0 |
---|
PDMC - Business Services | Business Services | Justin | The Practical Data Model for CMDB | v1.0 | L2 - Business Services. Considerations regarding this data model: - Note that the "Business Service" or "Service" class in ServiceNow has many use cases. Multiple logical classes in the PDMC are using the Business Service class. - Are all the different "services" in scope: business services, service products, service packages, customer facing service and backend services. - Role of the Business Process can vary based on requirements and overall data scope | 1.0, 1.1 |
---|
PDMC - Customer-Facing Services - Service Offerings | Customer Facing Services | Justin | The Practical Data Model for CMDB | v1.0 | L2 - Customer Facing Services - Service Offering. Considerations regarding this data model: - Responsible persons and groups can be defined on different levels - Business Service class has multiple usages in ServiceNow compared to different logical classes in the PDMC. - Service Portfolio might have a hierarchy using Service Taxonomies. | 1.0 |
---|
PDMC - On-Premise Business Applications - Application Services | On-Premise Business Applications | Justin | The Practical Data Model for CMDB | v1.0 | L2 - On-Premise Business Applications - Application Services. Considerations regarding this data model: - "Business Application" in the PDMC is mapped to "Application Service" in ServiceNow - "Business Application" class in ServiceNow is for APM that is out-of-scope from the PDMC - Change the "Service Configuration" related classes Application and Server to match your middleware, infrastructure and capacity plans. | 1.0, 1.1 |
---|
PDMC - SaaS Business Applications - Application Services | SaaS Business Applications | Justin | The Practical Data Model for CMDB | v1.0 | L2 - SaaS Business Applications - Application Services. Considerations regarding this data model: - "Business Application" in the PDMC is mapped to "Application Service" in ServiceNow - "Business Application" class in ServiceNow is for APM that is out-of-scope from the PDMC - Change the "Infrastructure Service" class to match with your choice of CI classes to represent cloud platforms. | 1.0, 1.1 |
---|
PDMC - Databases - Clustered | Databases | Justin | The Practical Data Model for CMDB | v1.0 | L2 - Databases - Clustered. Considerations regarding this data model: - In this model, DB instance is running on a cluster, another template for single server instances | 1.0, 1.1 |
---|
PDMC - Databases - On Server | Databases | Justin | The Practical Data Model for CMDB | v1.0 | L2 - Databases - On Server. Considerations regarding this data model: - In this model, DB instance is running on a server, another template for instances running on a cluster. | 1.0, 1.1 |
---|
PDMC - End User Devices - Personal Computers | End User Devices | Justin | The Practical Data Model for CMDB | v1.0 | L2 - End User Devices - Personal Computers. Considerations regarding this data model: - Asset related classes, if Asset Management is in use - Changing Desktop Software to Software Installation class if SAM plugin is in use. | 1.0 |
---|
PDMC - Server Capacity - Physical Servers | Server Capacity | Justin | The Practical Data Model for CMDB | v1.0 | L2 - Server Capacity - Physical Servers. Considerations regarding this data model: - One could have separate blueprints for clustered and non-clustered servers. - If server capacity is sold directly to a customer, then a Customer Facing Service Offering should be linked too. - Physical servers should have a link to "location" one way or another (via Data Center, more detailed Rack or simply location reference) | 1.0, 1.1 |
---|
PDMC - Server Capacity - Virtual Servers | Server Capacity | Justin | The Practical Data Model for CMDB | v1.0 | L2 - Server Capacity - Virtual Servers. Considerations regarding this data model: - One could have separate blueprints for clustered and non-clustered servers. - If server capacity is sold directly to a customer, then a Customer Facing Service Offering should be linked too. - Virtual servers should have a link to "virtualization cluster" or other virtualization CI that may be a virtualization technology-specific CI class. Just the "virtualization cluster" works for a more generic approach, especially if maintained manually. | 1.0, 1.1 |
---|
PDMC - Data Centers | Data Centers | Justin | The Practical Data Model for CMDB | v1.0 | L2 - Data Centers. Considerations regarding this data model: - Service Offering relationships can be on several levels - Servers may be related to a Rack via an Enclosure | 1.1 |
---|