Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 for HPE GreenLake Flex Capacity > Working in Cloud Cruiser > Onboarding FC customers > Creating a workbook

Creating a workbook

An ETL (extract-transform-load) workbook is where you configure the collection, transformation, and publishing of data into the Cloud Cruiser database. A workbook can contain one or more collections, each of which is a set of instructions for collecting a specific set of data from a single data source.

A workbook also contains one or more worksheets, similar to sheets in a Microsoft Excel file. A worksheet contains a flow, a progression of steps that process data, and a grid that displays sample data so that you can see the results of each step as you develop it. You can add to the flow whichever steps you need to manipulate your collected data, but the flow will most often start with an Import Collections step, which brings rows of data from one or more collections into the worksheet so that they can be processed, and most often end with a Publish Data step, which publishes the rows of data to a schema in the Cloud Cruiser database.

For users familiar with previous versions of Cloud Cruiser, a workbook is the equivalent of a process in batch XML, and each collection and flow the equivalent of a job.

Workbooks for HPE FC

Some of the processing that was previously done in customer specific batch jobs is now done in the workbooks. These workbooks perform common tasks prior to invoking the customer jobs, which simplifies the creation and maintenance of those jobs.

Global workbooks

Global workbooks are used to perform global tasks, or tasks that are common to multiple customer jobs. Generally, these workbooks are the first to run on any new processing day as they prepare data for the other workbooks to use. Examples of global workbooks include:

  • _DownloadUsage, which retrieves usage files for all customers from the mail server, and also performs preliminary processing for some types of resources, such as 3PAR, P2000, and StoreOnce.
  • _ProcessUsage, which processes usage files and performs additional transformations that are common for all customers. For example, the workbook converts all usage units to GiB, creates common dimensions (such as IP Address, hostname, and device type), and then copies the transformed usage files into the ${env.processDir}/_byCustomer directory, within a directory specific to each customer. With this structure, customer-specific jobs need only a single collector to retrieve usage files for the customer-specific workbooks.
  • _CapacityAlerts, which sends alerts if capacity or changes in capacity exceed certain thresholds. This runs at the end of the day, after all customer workbooks have been run.

Customer-specific workbooks

Customer-specific workbooks process usage data for specific customers, and publish it to the Cloud Cruiser database. Create customer-specific workbooks from the FC Customer Template and Services Template workbook templates. The Services Template workbook contains the following worksheets for each type of resource supported by FC:

  • _3PAR (Storage)
  • Blades (Charging for servers based on whether they are powered on)
  • Bulk-DL-Servers (Charging for servers based on whether they are powered on)
  • FixedCharges (Charging for service(s) that are not based on usage)
  • Memory (Charging for servers based on memory)
  • P2000 (Storage)
  • PerCoreUtil (Charging for cores based on what the core utilization is, i.e. 3%)
  • PerHostVM (Charging for servers based on whether they have any active VMs)
  • SAN (Switches)
  • SDS_LeftHand (Storage)
  • StoreOnce (Storage)
  • SynergyCompute (Servers)
  • SynergyStorage (Storage)
  • VM1.0 (Charging for VMs based on VM size)
  • VM2.0 (Charging for VMs based on compute units, or CUs, which is memory allocated to active VMs)
  • Several worksheets for Azure
    • AzureUsage
    • AzureTiers
    • PC_Usage
    • PC_MonthlyDiscounts
    • PC_MonthlySupport
    • PC_MonthlyCharges
  • Several worksheets for XP7 to provide for Thick, ThP, and SMRT pools, or based on configured groups:
    • XP7
    • XP7-Thick
    • XP7-Thin-ThP
    • XP7-Thin-SMRT-Tier1
    • XP7-Thin-SMRT-Tier2
    • XP7-Thin-SMRT-Tier3

The template worksheets perform some common steps, such as importing the usage data collected, retrieving the customer account structure, setting the location (if needed), setting the tier (if needed) identifying equipment features, and publishing to a specific schema. Additionally, some worksheets perform resource-specific steps. For example, the _3PAR worksheet uses aggregation to sum the capacity for all equipment in the array, while the XP7 worksheets calculate measures based on the tier. Because the steps in each worksheet are predefined, they can be used with minimal editing when onboarding FC customers. 

Creating a customer-specific workbook

Before you create a customer-specific workbook, you must select a unique 5-digit customer ID to represent the customer in Cloud Cruiser workflow. This number is part of the Account ID that is assigned to every new customer by the FC Technical Support Team.

To create a customer-specific workbook from a template

  1. In Cloud Cruiser, click Data > Workbooks.
  2. In the Workbook tab, click New.
    A dialog box appears.
  3. Enter a Workbook Name, and optionally a Workbook Description. The name should start with the 5-digit customer ID followed by a dash and user-friendly customer name with no spaces. For example, 00021-AceRun.
  4. Click Create Workbook from Template, select FC Customer Template, and then click OK.

    A new workbook is created, with just an empty worksheet called RemoveMe.
  5. Add services to the workbook, based on what is specified in the amendment form for the customer:
    1. Click the Copy icon in the Worksheets box in the top panel:
    2. Select Copy Sheets from Template.
    3. Select Services Template in the Workbook field, check the services used by the customer, then click Copy.
    4. Right-click the RemoveMe worksheet and select Delete Sheet.
    5. In the confirmation box, click OK.
  6. Click Save to save your progress in the new workbook.

Understanding how workbooks publish to schemas

Cloud Cruiser schemas provide the structure into which data is published from workbooks to the Cloud Cruiser database. Schemas allow data to be organized by type, enabling for easier and faster reporting from multiple sources of data.

Schemas defined for FC

The following schemas are predefined for FC:

  • Azure Services
  • Memory
  • Miscellaneous
  • SAN
  • Server
  • Storage
  • StoreOnce
  • VM1.0 Virtual Machine
  • VM2.0 Virtual Machine

You can manage these and other schemas on the Schema Management page of the Cloud Cruiser Portal by navigating to Data > Setup > Schema Management.

The following table lists the schemas to which services are mapped by any workbook based on the FC Customer Template workbook template:

Service Schema
3PAR Storage
Azure Azure Services
Blades Server
Bulk DL Servers Server
FixedCharges Miscellaneous
Memory Memory
P2000 Storage
PerCoreUtil Server
PerHostVM Server
SDS LeftHand Storage Storage
StoreOnce StoreOnce
SynergyCompute Server
SynergyStorage Storage

VM1.0 Virtual Machine

VM2.0 Virtual Machine

XP7 Storage

Types of data in schemas

Schemas include rows for the following types of data:

  • Measures: Fields containing quantitative usage information. They answer the question, "How much?" Examples include CPU Count, Memory Used, and Disk Size.
  • Dimensions: Fields containing qualitative or categorical information. They provide context around the value of a measure, answering questions like "What type?" and "When?" Examples include Serial Number, Port Name, and VM Id.

Publishing to schemas

Typically, the last step in each worksheet publishes usage data to a schema. Workbooks created by using the FC Customer Template workbook template already have the publish step configured for each worksheet, with columns mapped to appropriate fields.

Columns in a workbook can be mapped to the account structure, or dimensions or measures in the schema, but not all fields in the schema must have workbook columns mapped to them. Only required fields must be mapped. For example, the SAN schema has three required fields: Customer IdWWN, and Used.

When viewing the publish step in a worksheet, you can see the following areas for defining how data is published to a schema:

  • Account structure section: Ensures that usage data is mapped to the right accounts in the account structure.
  • Schema section: Maps usage data to fields in a schema.


Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP