cynthyap 110000GC4C Marcações:  virtual-infrastructure cloud_cost_management cloud-computing cloud virtualization 4.636 Visualizações
Even though server proliferation can be partially addressed through virtualization, the usage of virtual and physical assets becomes complex to accurately assess or manage. Cost management is crucial to integrate into overall service management, especially with a move into cloud. This webcast discusses how to implement a financial management roadmap and the key requirements for cloud transparency-- the ability to allocate IT costs, usage, and value.
Register today: http://bit.ly/VXXxl3
IBM SmartCloud Cost Management now provides usage metering and reporting for IBM SmartCloud Provisioning (SCP). This is now available for download on the ISM Library here: http://www.ibm.com/software/ismlibrary?NavCode=1TW10UM08
This new capability allows you to collect usage information from SCP environments using the SCP High scale low touch (HSLT) commands. The new HSLT SCP Collector gathers usage data every hour and processes it once a day. Usage, Detail and Identifier data is stored on a daily basis. The usage data is then billed, stored and can be reported on on a monthly basis.
A sample job file is provided as part of this functionality to show how to bill each access-id for the high-water mark of allocated resources in the month. The sample job file, SampleHSLT_SCP.xml is divided into three separate jobs.
The first job, SCP_collect_HSLT_hourly_data is recommended to be run every hour at XX:59. This job will run HSLT commands to collect all relevant resources for each access id that is using the SmartCloud Provisioning Service. Firstly, a list of all available access ids is collected using the command iaas-describe-accesses-by-user.
Then, for each access id, the command iaas-describe-resources-inuse-by-access is run to collect the relevant resources for that access id. The resources gathered per access id include:
Memory (MB) , Volume (GB), Number of Virtual Processors, Number of VM Instances, and Number of static IP Addresses.
The HSLT commands also provide context information that feeds into the Account Code Structure. The Account Code Structure includes the following identifiers:
The second job, SCP_Process_daily_data is recommended to be run every day some time after midnight. This job will process the daily CSR file and extract the maximum value across the day for each resource for each access id. The resource values are then stored in the cimsresourceutilization table of the SmartCloud Cost Management database. Detail and Identifier data is stored in the cimsdetail and cimsident tables of the SmartCloud Cost Management database.
The third job, SCP_Process_monthly_data is recommended to be run once a month at the start of the month. It will process the last months worth of data from the cimsresourceutilization table. It will do this by extracting the maximum value for each resource for each access id. Billing is applied to the data using the relevant SmartCloud Cost Management rate codes and the processed data is then stored in the cimssummary table of the SmartCloud Cost Management database, allowing reports to be run on the data.
The sample jobs can be customized for other charging algorithms if desired. Examples include charging on a daily (or hourly) basis in addition to or instead of on a monthly basis. Tiered pricing logic can be applied to provide for having charging amnesty for users/departments that stay below a certain threshold.
Rates are defined for each resource. These rates are used for billing purposes.
Additions have also been made to the existing SmartCloud Cost Management KVM collector to include new resources and a separate job file has been included to to add some SCP context data to the Account Code Structure, achieved by running HSLT commands.
For information about the existing TUAM KVM collector refer to the following link in the TUAM 7.3 Information Center:
The new resources for the KVM Collector include Bytes Received, Packets Received, Receive Packets dropped, Receive Packet errors, Bytes Transferred, Packtes Transferred, Transfer Packets dropped, Transfer Packet errors, Log Size of VM Image, Size of VM Image on Disk.
The new Account Code Structure for the KVM Collector contains the following identifiers: Service Region, Group, Username, Access id, VM Name
The VM Name contains the Access id allowing the information collected from the Hypervisor to be related back to the SmartCloud Provisioning identifiers.
The following reports are sample reports run on a system that has collected data from one Service Region on a SmartCloud Provisioning System:
Top 10 Pie Chart
Invoice By Account Level
Note also that other existing SmartCloud Cost Management collectors can collect information from VMWare and Power hypervisors.
See the Information Centre (http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.ituam.doc_7.3/admin_win_dc/c_core_data_collectors.html) for details.
If you have any questions about this functionality, please contact John Buckley (John Buckley/Ireland/IBM) or Louise O'Halloran (Louise O'Halloran/Ireland/IBM).
marvin_goodman 11000085U5 Marcações:  cloud_cost_management cloud-monitoring smartcloudmonitoring 5.409 Visualizações
In February, the IT industry analyst firm Enterprise Management Associates (EMA) released its first Radar™ for Application Performance Management (APM) for Cloud Services report.
IBM scored above the norm on all five axes measured – Architecture & Integration, Functionality, Deployment & Administration, Cost Advantage and Overall Vendor Strength.In addition to garnering the highest scores of any vendor, IBM was also noted for demonstrating “an in-depth understanding of the complex factors that support quality Cloud deployments." EMA goes on to extol the virtues of IBM's APM solution, asserting that:
Echoing recent analyst briefings on the use cases and customer value proposition vision of SmartCloud Monitoring, EMA said “We are seeing a new role within IT organizations called the ‘Cloud administrator’. Some companies are using an existing virtualization person, skilled in VMware or other virtualization technology. It is really important for a company to have such a role, and to have designated “Cloud architects”, as these skills are necessary to take a cross-platform, hybrid approach to Cloud rollouts.”
Read the full EMA report at the following URL: http://w3-03.ibm.com/software/analyst/articles/ema/emaapm.pdf
Understanding IT Costs, Cost Variance and Budgets versus Actuals with New TUAM Cognos Reports and Dashboards
DLawson 27000369MF Marcações:  cognos tuam reports showback chargeback cloud_cost_management tcr accounting 13.143 Visualizações
The TUAM team are pleased to announce the delivery of a further 17 TCR Cognos reports. These enhance the existing TUAM reporting set plus allow you to:
Dashboards allow users to get an immediate understanding of the situation at-a-glance. As an introduction to Dashboards in Cognos, reports to demonstrate two methods for creating dashboards have been provided in this report pack. Users can build pages in Cognos containing reports as well as other Cognos navigation objects and set this to be their home page when accessing Common Reporting:
For more information about Dashboards, log on to the IBM Integrated Service Management library.
Two reports are also provided to allow users to understand how they are doing against their budget. The Line Item Budget report compares usage against budget at service level to help identify those services using more than their allotted budget. Similarly, the Client Budget Report is a new report showing a comparison of the client level budget with the actual charges for the client, with any deviations from the budget highlighted:
The Client Budget Report can also be used to help monitor the actual costs of a Cloud project. For example, the budget for different periods can be updated when you get a charges estimate for a new Cloud project and the report can then show the difference in what you were actually charged later. The difference will be as a result of server configurations or the duration of project changing after the estimate was produced. More details on this can be found in the cost preview blog entry here.
The Percentage report allows users to understand the charges by sub-client and service by showing the total charges and its associated percentage of the overall costs by both client and service. For cloud users, this allows you to drilldown to understand the distribution between projects and teams. Users can expand and collapse the report to get a full understanding of all the areas being charged.
Reports to compare both the charges and usage between periods have been provided in this report pack. The Cost Variance report compares the charges from the current and previous period by client and service providing an understanding of the changes in charges over time. Similarly, the Resource Variance report compares the usage in the same way so users can see in detail how usage is changing from period to period.
Drill Down Reports
Drill down through the account hierarchy and see the services being used by each client with the Application Cost Report. Cloud users can drilldown into their projects and teams to get an understanding of what resources are being used and their charges. Users can see the charges for each level in the Account hierarchy and the associated charge for each service and service group being used.
jhkeenan 270001K41A Marcações:  cloud_cost_management usage accounting metering chargeback showback 5.896 Visualizações
You can get some expert exposure to Tivoli Usage and Accounting Manager and our Cloud Cost Management solutions via our demo's and workshops at Pulse 2012. Please come along to see us if you are at Pulse this year.
The workshops are in the MGM Studio Ballrooms.
In this lab exercise, you learn how to use IBM Tivoli Usage and Accounting Manager (TUAM) for metering and also accounting for projects and servers in a IBM Service Delivery Manager or IBM Tivoli Service Automation Manager based Self Service Virtual Server Management Environment. You analyze accounting showback reports in a demonstration setup. Optionally, you can create your own cloud financial model with the Financial Modeler. You can enter budgets, select rate codes, distribute costs, calculate rates, and run comparison reports.
In this lab exercise, you learn how to use IBM® Tivoli® Usage and Accounting Manager (TUAM) to collect resource usage data, and to create an invoice and usage showback reports. Optionally, you can create your own financial model with TUAM Financial Modeler. You can enter budgets, select rate codes, distribute costs, calculate rates, and run comparison reports.
The labs will be hosted by our TUAM technical enablement specialist Joachim Schmalzried.
Please look out for us as well at the ISDM/TSAM Ped.
To learn more about the Cloud track at Pulse, see this site: http://www-01.ibm.com/software/tivoli/pulse/cloud/
XiaZhang 120000K78V Marcações:  chargeback cloud_cost_management maximo tuam maas 7.263 Visualizações
Pay as you go is one of the characteristics of cloud computing service. To provide such a service we need to track the usage data for each cloud offering. For example, in an IaaS cloud platform, the usage data is normally the CPU, Memory, Disk, Network. For a SaaS cloud offering like Maximo as a Service (MaaS), the usage data required to charge the cloud offering consumer may be the business usage data, such as:
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:
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.
jbuckley 2700019NHW Marcações:  cloud_cost_management tsam price tuam charges cloud costs isdm preview 1 Comentário 7.873 Visualizações
Most generally accepted definitions of Cloud Computing imply the notion of Pay per use. For a Service Provider this means defining how they intend to bill for Cloud Services, while for a Cloud enabled DataCentre in the enterprise this implies some form of showback/chargeback model. As for those consumers actually using the Cloud, they want to understand the financial implications (what will it cost?) before committing their workloads to it.
As a Cloud Provider
The following screenshots illustrate how the new cloud cost management capability delivers solutions to these problems. The new TSAM Extension for Usage and Accounting is available to download now via the ISM Library.
See the Prices for the different Cloud offerings and compare different options
The first dropdown in the view shown below shows the Offerings that are available to the customer. Offerings can be anything the Cloud provider chooses to make available, for example: Virtual Servers, Storage or even PaaS or Saas offerings. The consumer can see up front what the different rates are for each component, and compare these across different offering types.
See what it would cost per month to run a new project in the Cloud
In this example, we want to have one machine to run an Application Server and one machine to run a Database and we need additional Tier1 storage in order to store the database data. The calculator shows how much this will cost per month overall and in terms of the two Service Offerings that this particular Cloud provides.
Different customers can be assigned to different subscriptions
A subscription is a means to segment your customers into different groups such as by geography or customer type (direct, business partners etc).
In this example, the RATIONAL and TIVOLI customers are assigned to the US (United States) subscription. Customers with this subscription share the same set of available offerings and pay the same price for those offerings.
Offerings are defined once and then added to Subscriptions
Once they are part of a subscription, the actual rate values (price per unit) can be defined for each element of the offering template.
If you wish to join the TUAM group to get more involved in reviewing new features and testing beta capability, then let me know and I can send you an invite.
jbuckley 2700019NHW Marcações:  tsam cloud_cost_management cognos billing tuam isdm reports chargeback tcr costs cloud 2 Comentários 11.174 Visualizações
Tivoli Usage and Accounting Manager (TUAM) development are pleased to announce the release of the IBM® Tivoli® Service Automation Manager (TSAM) - Extension for Usage and Accounting v1.0.
This TSAM extension delivers cloud cost management capability by enhancing the integration, reporting and services between TUAM and TSAM. The extension allows cloud users to view historical invoice reports that show the charges associated with each project.
The Usage and Accounting v1.0 extension provides the following features:
The following table shows the evolution in the TSAM/TUAM integration.
The diagram below show how the Usage and Accounting v1.0 extension facilitates the integration between TSAM and TUAM.
For more information about the Usage and Accounting v1.0 extension, log on to the Information Center.
jhkeenan 270001K41A Marcações:  chargeback cloud showback metering tuam cloud_cost_management 1 Comentário 8.371 Visualizações
As businesses adopt cloud environments to control IT complexity, pool resources, and improve cost efficiencies, the TUAM development team have been engaged in evolving the usage and accounting capability in IBM Tivoli Usage and Accounting Manager (TUAM) beyond traditional Enterprise charge-back.
In such a shared cloud environment the ability to accurately assess which IT resources and services are being utilized, how much they are being utilized, and by whom is fundamental if service providers are to justify the cost of the IT resource and expense.
The latest release of IBM Tivoli Usage and Accounting Manager, Version 7.3, provides Cloud Cost Management for those businesses needing to understand the new and dynamic usage of shared IT resources in Cloud and Virtualized environments, and seeking to bill or charge business units for their share of resource use including compute, storage, networks, energy, and personnel.
Read more about the new TUAM Cloud Cost Management Extension v1.0 for Tivoli Service Automation Manager (TSAM) in our blog update.
IBM Tivoli Usage and Accounting Manager allows businesses to:
Additionally the development team are working to supplement these core capabilities with new price tiering and invoice preview features for Cloud administrators and consumers. These features will be provided to TUAM users via the IBM Integrated Service Management Library from October 2011.