- how many assets are managed in the cloud for how many days,
- how many service requests or work orders are processed
Tivoli Usage and Accounting Manager (TUAM) is well-known for its IT usage metering and chargeback capability. However, TUAM can also be used to track the business usage data. This blog entry will describe this TUAM solution designed for MaaS.
In this TUAM solution, the following steps are followed:
- A Maximo daily crontask is developed and set up to retrieve the usage data from Maximo DB and to create a CSR file with the business usage data.
- A Maximo virtual machine OS daily crontask is set up to transfer the CSR file to the TUAM server.
- A TUAM daily job plan is set up to process the CSR files based on the accounting information set up in the TUAM server
- The existing TUAM invoice reports are leveraged to provide new reports to showback the billing information.
The following paragraphs describe the details of each of the above steps.
In step 1, we developed MaaSMeteringCronTask.java to collect usage metering data, and to output into a CSR file based on the format required by TUAM. The sample usage data includes: how many assets has the status <> "DECOMMISSIONED", how many work orders were closed in previous day, how many service requests were opened in previous day. The usage data is recorded for each account. The account information is composed of Tenant Company ID + Maximo Instance Name + Maximo VM Hostname. This data is fed into the CSR file. Here is the sample CSR file:
In step 2, the CSR files will be transferred to TUAM server for processing. In Maximo VM, we configured one Linux cron task to transfer the CSR files.
In step 3, the usage data in CSR files are
processed by TUAM server. In order to do this, we first need to set up the TUAM
server including account code structure, rate group,
rate codes and job file.
The most important configuration in TUAM server for a usage based metering solution is to develop one job XML file and configure it to run. You can find the sample job xml file in the TUAM server you installed. In the job xml file for MaaS, we defined the Job with ID “MaaS”, this job has one process with 5 steps:
1) Scan – this step scans the CSR files with the date as a part of their name, and merges them into CurrentCSR.txt file
2) Integrator_Account_Code_Generation – this step adds the account code information into the usage data record by combining the value from TenantID, Hostname, Maxinstance with the defined length. The output data is in file AcctCSR.txt
3) Process – this step is a normal TUAM step to process the usage data to generate files Ident.txt, BillSummary.txt and BillDetail.txt.
4) DatabaseLoad – this step is a normal TUAM step to load the data from above 3 files into the database.
5) Cleanup – this step is to cleanup the old CSR files. You can turn off this step if you do not want to clean the CSR files.
In step 4, we used the out of box TUAM invoice report to review or showback the usage based metering and billing report for MaaS. You could develop any new reporting based on your requirements using the Cognos reporting embedded in TUAM.