Compliance Automation functional architecture

Compliance Automation is the ability to automatically audit active configurations against policies or gold standards and remediate noncompliance.

It requires:

  • Service awareness
  • Compliance rules and exception handling
  • Out-of-the-box compliance policies
  • ITSM integration

BMC provides:

  • Fine-grained configuration items
  • Comprehensive compliance content
  • Automated closed-loop remediation

The key metrics for Compliance Automation are:

  • Percent decrease in patch time. Automated reporting is not available.
  • Percent decrease in audit time. Automated reporting is not available.
  • Percent increase in device to admin ratio. This metric can be reported using the Dashboards Service Automation Productivity Pod.
  • Percent decrease in remediation time. This metric can be reported using BMC Event and Impact Reporting, under the Impact/Metrics branch, MTTR.

This section describes the functional architecture that supports the following capabilities:




The capability to ascertain the existence of applications and infrastructure within an IT environment, along with configuration and dependency details, in near real time.

Configuration Policy Management

The capability to enforce business-level policies on who and what can be changed within an IT environment.

Patch Management

The capability to prioritize, analyze, and disseminate patches at a service level using unified methodologies within a heterogeneous IT environment.

Change Tracking

The capability to give complete visibility into all configurations and report on compliance with business policies.

Configuration Compliance and Remediation

The capability to remediate compliance violations based on business policies.

Virtual Machine Lifecycle Management

The capability to provide self-service establishment and reclaiming of virtual and physical resources based on business-level policies.


The diagrams in this section depict the logical components of the system, the communication of the components to one another, and the products to which these logical components belong.

UML robustness diagrams describe the flow of information and components involved in a complex system. UML robustness diagrams are used throughout the functional architecture documentation to describe the various products and components necessary to implement specific capabilities within the BMC BladeLogic Automation Suite value paths.

Each capability is divided into Actors (a person), Boundaries (typically a graphical user interface or a console), Entities (a database, or other external user artifact in the system, such as a server), and Controls (usually a BMC product). Arrows between the various components indicate the flow of information between the components. The following symbols are used:



Actor — User role that interacts with a component in the system

Boundary — Component that represents an interface with which Actors interact

Entity — Domain objects within the system that typically present a persisted state of that object

Control — Components that connect Boundary and Entity components and implement some logic to manage the interaction between them

Use cases

Was this page helpful? Yes No Submitting... Thank you