CloudBlue Connect uses XLSX (Open XML) file format for the bulk import and export operations in the Usage management module. The same format of the file can be used for both manual and automated flows and file defines the scope of the processing transaction, i.e. once uploaded, the whole file gets validated and either accepted or rejected.
Currency in the file follows the ISO 4217 standard – https://en.wikipedia.org/wiki/ISO_4217.
All timestamps in the file follow the ISO 8601 format in the UTC timezone (and ONLY UTC is allowed).
Usage Report contains contain the following tabs:
Note that systems must reference those tabs by names and not assume the order of these tabs.
Instructions tab contains general information about the file format.
General information tab contains global attributes that are used to interpret the rest of the file data.
|1||report_name||Consumption report for November 2019|
|2||report_note||Anything vendor things is needed|
|6||usage_schema||defines the schema:‘TR’, ‘CR’, ‘PR’ or ‘QT’|
|8||currency||Currency defined by ISO 4217 (https://en.wikipedia.org/wiki/ISO_4217) e.g. ‘USD’|
Note that some of the fields like currency are conditional to the usage_schema used.
Categories definition tab contains lookup table to be used in other parts of the same file. At least 1 category must be defined. Example table:
|compute||Computational Resources||All of your virtual machines and containers fall into this category.|
|storage||Persistance Services||All of your blob storages are accounted to this category.|
|db||Databases||All of various databases fall into this category|
Where all IDs, Names and Description are defined by the Vendor.
Records tab contains actual list of charge records to be applied to the Commerce system in a generalized table as illustrated below:
With the following columns:
Where columns amount and tier are being used conditionally for different usage schemas as illustrated in the following paragraphs.
This schema is the simplest one as only Quantity component of the usage file is being used. Thus neither amount nor tier columns are being used, only quantity:
all of the calculations in the Provider systems are performed based on the quantity column.
This schema is very likely where most of the industry is heading to with Azure Modern and AWS taking the lead. In the PR schema Vendor reports T0 Price and other Tiers are calculated based on that value. Amount in this schema represents T0 price (price to the subscription owner):
and tier column is not applicable here.
In this schema, Vendor reports Cost in the scope of the distribution contract and prices for other tiers are calculated based on that.
Amount in this schema represents Distribution Contract Price (price to distribution contract owner). Note that marketplace_account_id (defined in ‘general’) plays an important role in this schema as cost must be applied from that level down:
amount in this schema represents price of Vendor to the Contract account and tier column is not applicable here.
In this schema, charges for all tiers are reported by the Vendor and are just applied by the Provider systems. Charges table uses ‘tier’ column in this case and allows to report charges to multiple tiers as illustrated in the following example:
where the same charge of the quantity 15.75 is applied to 3 tiers of the accounts with different amount.