Which two statements are true about assignment of charges and chargeback plans to cost centers
for self-service resources?
A.
No charges will be assigned to a cost center by default for a database resource in a Platform as
a Service (PaaS) zone, even if a chargeback plan is created for that type of database.
B.
Assignment of chargeback plans to cost centers is done at the individual resource level.
C.
Assignment of chargeback plans to cost centers is done at the resource type level.
D.
Assignment of chargeback plans to cost centers is done at the PaaS or IaaS zone level.
E.
A chargeback plan may be assigned to more than one PaaS zone.
Explanation:
I think C and D … but, it could be that “B” is correct too
Cost Centers
• Charges are allocated to cost centers.
• Every SSA (Self Service Application (SSA) Portal User) user is their own cost center.
• Create extra cost centers to reflect the business hierarchy.
• Add SSA users to your cost center hierarchy.
• VMs, databases, and WLS instances requested in the self service portal inherit the requester’s cost center.
• A default cost center captures charges for users not in the cost center hierarchy.
Use Cost Centers to Allocate Charges
• Charges calculated by the universal and extended charge plans are allocated to cost centers. Every self service user is effectively their own cost center, hence charges associated with their self service portal activity are allocated to them.
• To take advantage of chargeback’s ability to help track and recoup operating costs, you should build your own cost center hierarchy that reflects the hierarchy of your organization. Self service users can be then included in your hierarchy, after which charges for any servers or services they request will roll up to ascendant cost centers. laaS and PaaS ZONES can also be included if they are for the exclusive use of a single cost center.
• The cost center hierarchy can be built within Enterprise Manager Cloud Control 12c or imported from an LDAP server, allowing you to synchronize with your corporate hierarchy.
• Charges for any self service users not included in your cost center hierarchy roll up to the default cost center.
• Be mindful that chargeback will not know about your SSA users until they have requested resources from laaS and PaaS zones, and those zones must in turn be known to chargeback. This effectively means that you may have to revisit the cost center SSA user assignments as SSA users become known to chargeback.
Adding Targets
• Add your SSA zones as chargeback targets.
o Assign the universal or an extended charge plan to each zone.
o Do not assign cost centers to them.
• Requested VMs, database instances, and WLS instances will have the ZONE’S charge plans applied to them.
• Charges will be allocated to the SSA requester’s cost center.
Add Your Cloud Zones to Chargeback
• When using chargeback to calculate and allocate charges for usage of your Enterprise Manager Cloud Control 12c clouds, add the self service application laaS Zones and PaaS Infrastructure ZONES as targets to the chargeback application rather than the underlying servers. This is because self service users request resources at the ZONE LEVEL. Assign either the universal or an extended charge plan to the zones, but do not assign a cost center unless the ZONES ARE EXCLUSIVELY USED BY ONE COST CENTER. The virtual machines, database instances, and WebLogic Server instances requested by your SSA users will be allocated to THEIR COST CENTER and that is the position in your cost center hierarchy where the charges for their usage should ideally be accrued.
Recouping Setup and Operating Costs
• A key capability that Enterprise Manager Cloud Control 12c delivers is the ability to take the usage and utilization metrics gathered against targets, including those within your clouds, and apply charge rates to produce chargeback reports. By assigning the underlying cloud components and self service users to cost centers, you are able to report on and chargeback for both cloud infrastructure and self service usage. There is also a catch-all default cost center for unassigned targets and users. Self service users can view the charges associated with their cloud resources.
Reports for Cloud Administrators, Self Service Users, and Billing Systems
• Cloud administrators
o Cloud administrators can view chargeback reports from the chargeback homepage by navigating to Enterprise > Chargeback and selecting the Reports tab. Reports can be a summary or trending (showing a time scale) and can be filtered by date range, cost center, target type or target, and metric (charge, CPU Usage, Disk Usage, Memory Usage, Uptime).
External billing systems
• Using the Enterprise Manager command-line interface (emcli) get_metering_data command, administrators can extract metering data from the chargeback schema that can then be imported into external billing systems. The following parameters can be used:
o start_date and end_date: If either or neither is specified, data for the latest reporting cycle is printed.
o charge: Print charge data. If not specified, usage data is printed.
o cost_center: Internal name of the cost center to report upon. If not specified, the cost center of the user logged in to emcli is used.
o target_type: Optionally, restrict the output to a particular target type. Allowable values are oracle_database, oracle_vm_guest, host, and weblogicj2eeserver. If specified, the target_name parameter must also be specified.
o target_name: If restricting output to a particular target type, optionally restrict output to an individual target.