Jump to: navigation, search

Business unit billing breakout

Description

PureEngage premise customers require ability to bill by business unit as sub-groups under the main customer or reseller. This applies to all products. Business unit should be implemented using the standard 3-tier hierarchy used in the IT billing process.

Metric Business unit attribution

seats_inbound_voice

seats_outbound

seats_chat

seats_email

seats_cobrowse

seats_third_party

seats_sms

seats_workspace

seats_social

seats_CIM

seats_agent_connector

GIM-based seats are attributed to a business unit based on the path to the corresponding Person object in the Configuration Management Environment (CME) folder structure:

The agent_resource dataset is used to get a DBID of the folder to which the agent belongs. sm_fact is joined with agent_resource on agentID field.

New "folder" dataset is used to determine the path to that Person object, and thus to attribute the agent session to a business unit.

voicemail_boxes

Voicemail boxes is attributed to business units based on the path to the corresponding configuration object of DN, Agent Login, or Agent Group types.

Path to the object is determined during a retrieval of the object from Configuration Server and recorded in the voicemail_agents_groups dataset, which is described in the Voicemail Boxes metric design.

gvp_ports

gvp_minutes

gvp_hybrid

gvp_asr_ports

gvp_tts_ports

gvp_asr_minutes

gvp_tts_minutes

GVP activity is attributed to a business unit based on the CME location of any resource of the call, where CALLID is present in the GVP CDR record.

After test voice interactions are filtered out, records that have the same value of the CALLUUID as the CDR's CALLID are collected from 'tfn_durations' and 'pstn_durations' datasets.

If any of the found records can be attributed to a business unit using the rules described in the 'pstn_inbound' section the CDR is attributed to that business unit.

Otherwise, the CDR is attributed to a 'default' business unit.

For information on configuration, see business unit billing breakout configuration.

Resulting files format

Tier3AccountID and Tier3AccountName fields in the resulting files are used to populate configuration unit information.

If business units are configured for a given tenant, additional files for each business unit, plus a file for a default business unit are generated, and the Tier*AccountID, Tier*AccountName fields are populated as below:

  • Tier3AccountID - unique ID of the business unit
  • Tier3AccountName - unique name of the business unit
  • Tier2AccountID - unique ID of the tenant
  • Tier2AccountName - name of the tenant

Default business unit name and ID are formed as <tenant_id>_BU_0.

Business unit blacklist

Beginning with release 9.0.000.18, BDS supports a business unit blacklist. Business units that are added to the blacklist cannot be added or imported; this prevents errors during business unit name detection. The blacklist is defined in the gvars.py file:

BUSINESS_UNITS_NAMES_BLACKLIST = [
'agents', 'dns', 'persons', 'campaigns', 'switches',
'configurations', 'agent logins', 'campaign groups'
]

You can print the blacklist to the console using the brsctl.py utility, as follows:

python brsctl.py units -t <tenant_name> -bl
This page was last modified on January 22, 2019, at 18:34.

Feedback

Comment on this article:

blog comments powered by Disqus