This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Calbro scenario for normalization

The following common scenario is used to explain normalization features and processes throughout the normalization documentation. This scenario builds on the Calbro Services scenario in How Calbro Services planned normalization and Product Catalog implementation.

Calbro has four datasets that must be configured for normalization, each corresponding to a different data provider, as illustrated in the following figure. To design the Calbro normalization processes, Calbro staff are required to have the following roles:

  • Data modeler — To answer questions about data requirements and the data model, including Calbro customizations and extensions.
  • Software distribution engineer — To decide what software is distributed electronically and to decide what types of discovered products should be added to the Product Catalog.
  • Integration specialist — To lead and design integrations and to make sure integration architecture can be maintained and work with Calbro's architecture.
  • Process analyst — To make sure that the normalization processes and decisions support Calbro's business needs.

Calbro's data providers

Calbro's staff has analyzed the company's needs and answered the normalization questions to design its normalization processes.

Calbro's normalization analysis


Calbro's answer

Must more than one dataset be reconciled to the BMC.ASSET production database?

Yes — Calbro has four different datasets that must be set up for normalization before they can be reconciled and added to BMC.ASSET.

Should discovered products that do not exist in the Product Catalog be added automatically?

Yes — Any instances in CALBRO.APPS should be used to create Product Catalog entries if they do not exist. CALBRO.APPS contains a list of all the applications that Calbro has developed. Calbro trusts this data because they created it manually and consistently.

Should data be normalized as it is being written to BMC Atrium CMDB (inline mode)?

Or, should data be normalized after it is written to BMC Atrium CMDB —

  • and after a certain number of changes have been made, or after a certain amount of time has passed (continuous mode)?
  • at a scheduled time (batch mode)?

InlineCALBRO.APPS is a list of Calbro applications which is updated with new versions and patches. Because this data source has a high volume of changes, Calbro sets this dataset to inline normalization so that, if needed, new Product Catalog entries can be created from these instances.
Continuous — Calbro initially normalizes CALBRO.DISC with a batch job and then sets to continuous normalization after 20 modifications or creations. Because of the importance of maintaining their e-commerce services, Calbro wants updated and new instances to be normalized and reconciled as quickly as possible without a significant impact on other users and processes.
Batch — Because BMC.ADDM and BMC.IMPORT.BL have a large number of changes, Calbro schedules normalization of these instances during off hours.

Do any datasets not require normalization?

NoCALBRO.APPS contains a list of all the applications that Calbro has developed. Calbro trusts this data because they created it manually and consistently. Calbro uses this dataset to create Product Catalog entries.

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