Default language.

Important This documentation space contains information about the SaaS version of BMC Helix Discovery. If you are using the on-premises version of BMC Helix Discovery, see BMC Helix Discovery 25.2 (On-Premises).

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-modelsBMC Helix AIOps

Blueprints

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.

Blueprints in BMC Helix Discovery and BMC Helix AIOps

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

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 uniquely identifying the entity in the environment. In  BMC Helix AIOps, a node kind is known as a CI Kind.

    For information about the node kinds supported by BMC Helix AIOps, see Understanding-service-blueprints in the BMC Helix AIOps documentation.

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*