Service modeling with blueprints

Defining a service enables you to efficiently manage the underlying applications and infrastructure that is relevant to your business needs. Blueprints are templates that give you complete control of the service that you are modeling. You can use both static and dynamic content to control the model composition. 

Related topics

Service and application modeling

Managing models BMC Helix AIOps Open link


Blueprints are predefined service templates or building blocks to be used by organizations for defining services when creating service models. Blueprints visually map out the steps that make up a service process, and make it simpler to design a new service, or improve an existing service. Blueprints play a significant role in managing service operations, service design, and service positioning.

Blueprints in BMC Helix Discovery include nodes that can be defined to have static or dynamic rules. Each blueprint contains one or more nodes of the same kind, interconnected to define a relationship.

Based on your organization's need, you can define a blueprint to:

  • Start with an application node, such as Namespace, and have the rest of the service contain one or more applications and infrastructure nodes. You can then use these applications and infrastructure nodes to create an application to infrastructure map.
  • Start with an infrastructure node, such as Host, and have the rest of the service contain one or more applications and infrastructure nodes. You can then use these infrastructure and application nodes to create an infrastructure to application map.

Can I use the same blueprint multiple times?

- The same blueprint cannot be used more than once in a service model.

- You can use the same blueprint in different service models.

- You can use a combination of blueprints in service models.

Blueprints in BMC Helix Discovery

Global flags in Python are meant to be placed at the start of regular expressions. Earlier versions of Python issued warnings for misplaced flags. BMC Helix Discovery now uses Python 3.11, in which misplaced flags are an error. TKU patterns have been updated for this change, and the TPL compiler now warns if flags are misplaced in your custom patterns. However, regex searches with misplaced flags fail silently. In Blueprints, the searches fail to match and, without notification, your Blueprints will be empty, or will not contain what you expect.

A simple example of a misplaced flag is: '^(?i)Linux' which can be corrected to '(?i)^Linux'

Similarly: '/Common/(?i)((FV|dl)515sy):2121' can be corrected to '(?i)/Common/((FV|dl)515sy):2121'

An example from the EMC ControlCenter StorageScope pattern is: '^(?i)EMC ControlCenter \d(?:\.\d)*' which has been corrected in the TKU to '(?i)^EMC ControlCenter \d(?:\.\d)*'

Blueprints in BMC Helix Discovery and BMC Helix AIOps

Blueprints developed in BMC Helix Discovery can be viewed, used and modified in BMC Helix AIOps. Equally, those created in BMC Helix AIOps can be viewed, used and modified in BMC Helix Discovery.


Becky is a service designer at APEX Global. A request is sent to Becky to create new services to manage the operations of her organization. While creating the service models to map these services, Becky realizes that there are a few common processes that are part of each of these service models. For example, the Kubernetes cluster service and virtual applications management service are essential common basic services that are part of many other services, such as Kubernetes deployments, network availability monitoring, virtual data center operations, and so on. Becky defines the common basic services such as Kubernetes deployment, network availability monitoring, and virtual data center operations, as blueprints.

Nodes and node kinds 

  • A node is an object that represents an entity in the environment discovered by BMC Helix Discovery and stored in the datastore. Nodes can be connected to other nodes by using relationships.
  • A node kind is the type of a node, such as a Host or Software Instance. The default set of nodes and their named attributes and relationships are defined in the BMC Helix Discovery taxonomy. A node kind can also have extended attributes. Although the extended attributes are not defined in the BMC Helix Discovery taxonomy, they are used by some CIs in BMC Helix AIOps. Most node kinds have a key that uniquely identifies the entity in the environment. In BMC Helix AIOps, a node kind in known as a CI Kind.

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