Page tree

Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

BMC Impact Model Designer is a plug-in integrated into BMC Atrium Core Console. BMC Impact Model Designer allows BMC ProactiveNet users to create and design service impact models.

When publishing server runs in an automated mode, the promotions in the Impact Model Designer automatically terminates a publication.

BMC Impact Model Designer is leveraged from BMC Atrium Explorer and uses the same user interface as that of BMC Atrium Explorer. You can use both of these products to create service models. However, BMC Impact Model Designer contains some unique functionality not available in BMC Atrium Explorer.

The following software must be installed in the following order before using BMC Impact Model Designer:

  1. Oracle or Microsoft SQL Server (to be used as a database for BMC Atrium CMDB)
  2. BMC Remedy Action Request System
    BMC Remedy Action Request System is the software through which you can access the BMC Impact Model Designer interface. For information about installing BMC Remedy Action Request System, see the BMC Remedy Action Request System Installation Guide located on the [ BMC Support website|] .
  3. BMC Atrium CMDB suite
    BMC Atrium CMDB is the database in which CIs are recorded and maintained throughout their life-cycle. For information about installing BMC Atrium CMDB suite, see the BMC Atrium Core Installation Guide located on the BMC Support website .
  4. BMC ProactiveNet
    BMC Impact Model Designer is a part of the installation of BMC ProactiveNet CMDB Extensions and is automatically installed when you install BMC ProactiveNet CMDB Extensions. For information on installing these extensions, see Installing BMC ProactiveNet CMDB Extensions.

See System requirements and product compatibility for the minimum supported configuration requirements, and supported versions.

Prerequisites to using BMC Impact Model Designer:

BMC ProactiveNet Administration Console and BMC ProactiveNet Operations Console are the interfaces through which you can view the service impact models created through BMC Impact Model Designer and published by BMC ProactiveNet Publishing server.

Creating an AR user for service model creation

  1. Log in with the user tool Object List and search for Group form.
  2. From the list that displays, double-click Groups.
    The Groups form opens. Press F5 to search for all existing groups.   
  3. Select the BPPM Model Administrators group.
  4. Open Object List and search for Roles form.
  5. From the list that displays, double-click Roles.
    The Roles form opens. Press F5 to search for all existing roles.
  6. Select the CMDB Data Change All role.
  7. In the Production mapped group drop-down list, select BPPM Model Administrators.
  8. Click Save.
  9. Open Object List and search for User form.
  10. From the list that displays, double-click User.
    The User form opens.
  11. Click New request to create a new user.
  12. Provide the following information:
    Login name = bppmadmin
    Full name = bppmadmin
    Password= bppmadmin
  13. In the Group List drop-down list, select Full Access or Service Administrators.
  14. In the Dynamic Group Access drop-down list, under the Password Management area, select BPPM Model Administrators.
  15. Select the License Type, either Fixed or Floating.
  16. Click Save?
  17. Log in with this ID.

You now need to manually perform the integration from BPPM Server. Run the post-CMDB integration utility integrate_atrium_cmdb and pass all mandatory parameters.


A sandbox is a personal work area for designing and developing a service model. You can make changes to objects and their relationships, and save these changes between work sessions, without affecting the production environment until you are ready to move the changes into the production dataset.

BMC Impact Model Designer users have their own unique, dedicated sandbox, and sandboxes persist between user sessions, allowing you to make multiple edits to the sandbox model until you promote the changes to the production dataset. Each user has one sandbox associated with the user account. Changes to your sandbox do not affect sandboxes of other users if those changes are not promoted.


The production dataset is the reference dataset, or logical partition of data in the BMC Atrium CMDB, shared by service model applications. Objects contained in the production dataset are components, relationships, and management data.

When working with objects in a sandbox, users are making changes to an overlay dataset, a dataset which is related to and masks the production dataset. The overlay dataset provides a view of the underlying production dataset masked by changes made by the user in the overlay dataset.


You move changes that you make in a sandbox (on the overlay dataset) to the production dataset in a controlled process called promotion. When a promotion completes successfully, changes in the sandbox are merged with changes from other users and processes in the BMC Atrium CMDB. As soon as you successfully promote changes to a production dataset, the sandboxes of all other users are updated to reflect the new data.

Promotion and automated publishing process

Promoting and publishing are a sequence, in which you initiate a process to push objects (new or changed) to the BMC Atrium CMDB, followed by the automatic publication process, which sends that data to appropriate BMC ProactiveNet cell.

1 Comment