Hybrid Business Management Configure Hybrid Business Management

Edit online

For release notes, see About HBM .

For reports, see the HBM Report Matrix .

Hybrid Business Management (HBM) offers two configuration options:

Rate-based - This option leverages rate cards to speed up delivery instead of loading cost source data and mapping cost centers to IT resource towers.

G/L-based - This option brings in actuals and budget data, then maps them to cost pools and sub-pools. Also, this approach maps cost centers to IT resource towers.

HBM rate-based configuration

  1. Install the Hybrid - Infra Rates component.
    This step installs the Infrastructure Rate Card master data set, which allows you to leverage predefined columns for your rate card. The columns are designed to either stay at the IT tower and sub-tower level or go down to next level, which is beneficial if you use T-shirt sizes for Servers (for example, Small, Medium, Large, Jumbo).
  2. Import rates using the usual data loading process.
    Example rate card:

  3. Click Map Columns to map the rate data using one of the following drivers:

    • Price times Quality (P*Q) driver - Populate the columns as follows:
      1. Map the IT Resource Sub Tower Name source tower to "IT Resource Sub-Tower Name."
      2. Map the IT Resource Tower source tower to "IT Resource Tower."
      3. Map the Quantity source tower to "IT Resource Tower Quantity."
      4. Map the On-Prem source tower to "Delivery."
      5. Add a new column called "Price."
      6. Map the Unit of Measure source tower to "Unit of Measure."
        Example of columns mapped to IT Resource Towers Master Data using the Price driver:
    • Amount driver - Populate the columns as follows:
      1. Map the IT Resource Sub Tower Name source tower to "IT Resource Sub-Tower Name."
      2. Map the IT Resource Tower source tower to "IT Resource Tower."
      3. Map the Quantity source tower to "IT Resource Tower Quantity."
      4. Map the On-Prem source tower to "Delivery."
      5. Create a formula step in Raw Data to multiply Price times Quantity to get your amount.
      6. Add new column called "Amount."
      7. Map the Unit of Measure source tower to "Unit of Measure."
        Example of columns mapped to IT Resource Towers Master Data using the Amount driver:
    1. (Optional) Map the rates to the lower level under IT Resource Sub-Tower by defining the Resource Metadata 1 and Resource Metadata 2 columns. Ensure that these columns are within the object identifier on the IT Resource Towers object.
    2. Open the IT Resource Towers model object and create one of the following:
      • P*Q - In IT Resource Towers, add the following driver to Formula for the Cost model:
        =IT Resource Towers Master Data.IT Resource Tower Quantity*IT Resource Towers Master Data.Price
      • Amount - In IT Resource Towers, add the following driver to Cost model:
        Column=IT Resource Towers Master Data.Amount

G/L-based configuration

HBM is typically configured to map actuals and budget data to cost pools and sub-pools, then map the Cost Source object to the Servers object. Costs are then directed to the Cloud Migration model, which compares actual server costs to the cost of cloud service providers.

Step 1: Update the catalog data sets

  1. Install the Hybrid - Migration component.
  2. Go to Project Explorer > Tables > Server Migration , and check out the following master data sets:
    • AWS Azure Google Mapping
    • AWS Compute Price Reference List
    • Azure Compute Price Reference List
    • Google Cloud Compute Price Reference List
      TIP : The Server Migration table contains transforms for Azure and Google Cloud, but AWS transforms are appended directly to the AWS Price List Master Data so they are not listed separately.
  3. In each data set, click the Reference Table step, then click Update Reference Data .
    Note : A notification in the reference table step lets you know whether a newer version of the document exists.

After the reference price lists are updated, they are automatically transformed and appended to their respective master data sets.

Step 2: Map the cloud servers

This step sets up the allocations and lookups necessary for the Migration Comparison and Utilization Comparison reports.

  1. Go to Tables > Cloud Server Mapping .
    This data set contains the mapping for your cloud server locations for AWS, Azure, and Google Cloud.
  2. Upload your on-premises cloud hosting locations and map them to the AWS, Azure, and Google locations.

Step 3: Map data to the Server Migration Master Data

Transform your physical servers from the Server Master Data or raw data set to the Server Migration Transform.

  1. In Project Explorer, go to Tables > Server Migration > Server Migration Master Data to open the Server Migration Master Data table.
  2. Append the physical servers or Server Master Data into the Server Migration Master Data. The following columns are required:
    • Migration analysis and the Migration Comparison report:
      • Server ID
      • CPU Cores
      • Memory Capacity
      • Location
      • Server Hours – If this data cannot be sourced, we recommend you input 720 hours.
      • Storage Capacity
      • OS
    • Valuable migration reporting:
      • Class
      • Environment
      • Platform
      • Vendor
    • The Workload/Application view:
      • App Consumer
      • Application
      • The same columns used for migration analysis and the Migration Comparison report.
        Note : To get full view into your workloads, the application/workload that is mapped to a given server ID must have parity with the application name/ID in the Applications Master Data.
    • Utilization analysis and the Utilization Comparison report
      • CPU Peak Usage – Into this column, map the average of the peaks for a given server over the course of a month.
      • Memory Peak Usage – Into this column, map the average of the peaks for a given server over the course of a month.

Step 4: Validate HBM allocations

  1. In the Project Explorer, go to Metrics > Cloud Migration Model .
  2. Open the AWS Price List Model step, and verify that the allocation line from AWS Price List to Server Migration shows a data relationship in the following columns:
    • AWS Price List Master Data.AWS Server = Server Migration Master Data.Recommended EC2 Instance
    • AWS Price List Master Data.Location = Server Migration Master Data.AWS Location
    • AWS Price List Master Data.OS Category = Server Migration Master Data.OS
  3. Enter the following P*Q formula, which intentionally over-allocates:
    =SOURCE*Server Migration Master Data.Server Hours
  4. Open the Azure Price List Model step.
  5. Verify that the allocation line from Azure Price List to Server Migration shows a data relationship in the following columns:
    • Azure Price List Master Data.INSTANCE = Server Migration Master Data.Recommended Azure Instance
    • Azure Price List Master Data.LOCATION = Server Migration Master Data.Azure Location
    • AWS Price List Master Data.OS Category = Server Migration Master Data.OS
  6. Enter the following P*Q formula, which intentionally over-allocates:
    =SOURCE*Server Migration Master Data.Server Hours
  7. Open the Google Price List Model step.
  8. Verify that the allocation line from Google Price List to Server Migration shows a data relationship in the following columns:
    • Google Price List Master Data.Machine type = Server Migration Master Data.Recommended Google Instance
    • Google Price List Master Data.State = Server Migration Master Data.Google Location
  9. Enter the following P*Q formula, which intentionally over-allocates:
    =SOURCE*Server Migration Master Data.Server Hours

Step 5: Configure Hybrid Additional Costs Master Data

The Hybrid Additional Costs Master Data table allows you to input cloud discounts/credits, sales tax, and support costs, then use that data via lookup by Server Migration Master Data for individual cloud providers.

  1. To input the source data for your cloud providers, create a raw data set with discounts/credits, sales tax, and support costs for each of the cloud providers: AWS, Azure, and GCP.
    CAUTION : Use "AWS", "Azure" and "GCP" verbatim so the lookups and allocations work correctly.
  2. Check out the Hybrid Additional Costs Master Data table.
  3. Append the raw data set into Hybrid Additional Costs Master Data as follows:
    • Provider - Enter one of the following: "AWS", "Azure", or "GCP".
    • Express the discounts in decimal form as a percentage of overall spend.
      For example, for 10%, enter ".1", or for 5% enter ".05".
    • Express the sales tax in decimal form.
      For example, for 9.54% enter ".0954".
    • Express the support costs in aggregate for the given cloud provider.
      For example, if your AWS Support bill is $5,500, enter "5,500".

Support costs will be automatically modeled into the Server Migration Master Data set because they are reported only at the aggregate level.

HBM Components

Hybrid Business Management (HBM) uses the following components.

Hybrid - Migration

  • Data sets installed:
    • AWS Azure Google Mapping – via Catalog Services
    • AWS Compute Price Reference List – via Catalog Service
    • AWS Price List Master Data
    • Azure Compute Price Reference List – via Catalog Service
    • Azure Compute Price Reference List Transform
    • CPU Normalization
    • CPU Optimized EC2 Instances
    • Cloud Server Mapping
    • Google Cloud Compute Price Reference List
    • Google Cloud Compute Price Reference List Transform
    • Google Cloud Price List Master Data
    • Hybrid Additional Costs Master Data
    • RAM Normalization
    • RAM Optimized EC2 Instances
    • Server Migration Master Data
    • Utilization CPU Normalization
    • Utilization RAM Normalization
  • Model steps (objects):
    • AWS Price List
    • Azure Price List
    • Google Price List
    • Hybrid Additional Costs
    • Labor
    • Server Migration
    • Servers
    • Storage
  • Models:
    • Cloud Migration Model
  • Reports:
    • AWS Migration
    • Additional Use Cases
    • Migration Comparison
    • Summary
    • Utilization Comparison

Hybrid - Infra Rates

  • Data sets installed:
    • Infrastructure Rate Card Master Data

Hybrid - Workloads

  • Data sets installed:
    • Applications Master Data
    • Reports:
    • Workload Migration

Hybrid - Target Spend

  • Data sets installed:
    • IT Towers Target Spend Master Data
    • IT Towers Target Spend Raw
  • Model steps (objects):
    • IT Resource Towers
    • IT Towers Target Spend
  • Models:
    • Target Spend
  • Reports:
    • Infrastructure Variance

Hybrid - VMWare Private Cloud

  • Data sets installed:
    • CPU and RAM Rate Settings
    • vRA_VM Group Master Data
    • vROps Oversized VM Master Data
    • vROps Recommendations Master Data
  • Model steps (objects):
    • Servers
    • vROps Oversized VMs
  • Models:
    • Private Cloud
  • Reports:
    • Public vs Private Cloud
    • VMWare

Example configuration of Cloud Migration Model

The following images provide an example of a configured Cloud Migration Model.