Package Map

The Package Map file maps a TapeTrack Customer-ID to the billing package that applies to that Customer.

The map is used by TMSS10LogStatsProcess when processing TapeTrack statistics (.ttstats) files for billing.

The Package Map allows different Customers to use different billing rates and calculation rules while being processed through the same billing configuration.

For example, Customer US01 may use the STANDARD package, while Customer US02 uses the PREMIUM package.

The Package Map does not define the rates or billing calculations. These are defined in the Billing Rules.

The Package Map provides a consistent relationship between a TapeTrack Customer-ID and the approved billing package assigned to that Customer.

The file can be used to:

• Assign a billing package to each Customer.
• Apply different rates to different Customers.
• Allow several Customers to share the same billing package.
• Separate Customer package assignments from the Billing Rules.
• Maintain consistent package assignments across billing periods.
• Change a Customer's package without modifying the .ttstats file.
• Ensure billing is calculated according to the approved Customer Billing Profile.

The Package Map can be stored in any directory accessible to the account running the billing process.

For ease of administration, it is recommended that all approved billing configuration files are stored in a dedicated directory.

Example Windows location:

C:\Program Files\TapeTrack\TapeTrack Framework Server\etc\billing\package.txt

Example Linux location:

/etc/tapetrack/billing/package.txt

The location of the file is supplied to TMSS10LogStatsProcess using the -P argument.

The Package Map is a plain-text file.

Each mapping contains:

• The TapeTrack Customer-ID on the left.
• The billing package name on the right.

The general format is:

CUSTOMER-ID Package Name

Example:

When a billing record contains Customer-ID US01, the billing processor selects the STANDARD package and applies the corresponding Billing Rules.

The following example contains two TapeTrack Customers.

package_map.txt

#
# TapeTrack Billing Package Map
#
# Format:
# CUSTOMER-ID Package Name
#
 
US01 STANDARD
US02 PREMIUM

Lines beginning with a hash character (#) are comments and are ignored during processing.

Comments should be used to document:

• The purpose of the file.
• The expected mapping format.
• The available billing packages.
• Any Customer-specific package requirements.

The package name must correspond to a package defined in the Billing Rules.

For example:

Check that:

• The -P argument has been included.
• The specified Package Map file exists.
• The billing account has permission to read the file.
• The Customer-ID is present in the map.
• The Customer-ID matches the value in the .ttstats file.
• The mapping does not contain an unwanted leading or trailing space.
• The package name is present in the Billing Rules.

Confirm that:

• The correct Package Map file was used.
• The Customer-ID is not duplicated.
• The Customer is assigned to the approved package.
• The package name is spelled correctly.
• The package name matches the corresponding package in the Billing Rules.
• An old copy of the file is not being referenced by the billing script.
• The package assignment matches the approved Customer Billing Profile.

The Package Map may select the correct package while the rates defined in the Billing Rules are incorrect.

Check both configurations:

1. Customer-ID to billing package in the Package Map.
2. Billing package to rates and calculations in the Billing Rules.

Check that:

• The Customer is present in the Package Map.
• The assigned package exists in the Billing Rules.
• The .ttstats file contains billable activity.
• The Billing Rules contain rules matching the Customer's activity.
• The correct billing date range was extracted.
• The Package Map and Billing Rules use the same package name.

• Keep the file in a controlled billing configuration directory.
• Use one authoritative Package Map for each billing environment.
• Do not maintain uncontrolled copies.
• Use clear and consistent package names.
• Confirm that every billed Customer has a package assignment.
• Ensure package names match those defined in the Billing Rules.
• Review package assignments against approved Customer Billing Profiles.
• Test package changes before the production billing run.
• Restrict write access to authorized billing administrators.

The Package Map does not normally contain passwords or authentication details. However, it contains commercial information about the billing arrangements assigned to Customers.

Access should therefore be restricted to:

• TapeTrack administrators.
• Authorized billing staff.
• The service account that runs the billing process.

The file should not be publicly accessible or stored in an unsecured shared directory.

• TMSS10LogStatsProcess
• Customer Description Map
• Billing Rules
• Billing Process
• XMLQuickBooks Mapping