Home
MATRIXX Pricing and Rating
Pricing
Deploying a Pricing Plan
Deploying a pricing plan involves compiling the pricing plan into a configuration file and loading the configuration file into the pricing database. During compilation, the pricing schema is validated and any errors that occur are displayed.
Compiling Pricing Plans
When you compile a pricing plan, a pricing XML configuration file is generated from all pricing items and policy items in the pricing domain. The pricing XML configuration file can be generated as a standalone file during pricing validation or as part of a ZIP archive that contains the following additional files:

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
- About Pricing and Rating
  MATRIXX Pricing and Rating provides an introduction to MATRIXX pricing and rating functionality and describes how to define the catalog components necessary for rating and policy selection. It also provides an overview of the MATRIXX rating process and an introduction to My MATRIXX, a web-based user interface application you use to create and manage product catalogs.
- Rating
  The following information describes MATRIXX Charging Application rating functionality.
- Pricing
  - Pricing Overview
    The MATRIXX pricing model is highly flexible and enables you to create innovative service offerings and tailor pricing to subscriber needs. It is compatible with the TM Forum (TMF) Shared Information/Data (SID) model.
  - Pricing Data
    The MATRIXX Engine pricing data model is compatible with the Shared Information/Data (SID) standard, as defined by the TM Forum (TMF).
  - Pricing Corrections and Revisions
    Make corrections and revisions to all pricing items except balance classes, meter classes, balances, meters, and products. For information about product offer versions, see the discussion about product offers.
  - Updating Pricing After Purchase
    Not all pricing items can be updated after pricing is loaded and subscribers are using it.
  - Pricing Plans
    Pricing plans define the pricing and policies that allow you to control how you provide services to subscribers and how you are paid for those services. Pricing plans are comprised of catalog items, offers, bundles, and supporting objects required to implement pricing.
  - Planning a Pricing Plan
    Before you create a _glossary/pricing_plan.html, determine how you want to name, organize, and set up the items that form planning a pricing plan.
  - Deploying a Pricing Plan
    Deploying a pricing plan involves compiling the pricing plan into a configuration file and loading the configuration file into the pricing database. During compilation, the pricing schema is validated and any errors that occur are displayed.
    - Compiling Pricing Plans
      When you compile a pricing plan, a pricing XML configuration file is generated from all pricing items and policy items in the pricing domain. The pricing XML configuration file can be generated as a standalone file during pricing validation or as part of a ZIP archive that contains the following additional files:
  - Group-Owned Pricing
    Groups can own product offers that define service pricing for group members. The product offers can define pricing for both usage and non-usage event types.
  - Taxation
    MATRIXX supports two types of taxation: tax classes and selectors, and US taxation. Tax classes specify tax rates or fixed taxes, and tax selectors dynamically select the tax rate, and apply one or more taxes to a charge. US taxation determines the taxes for a given location, and specifies the tax type, product category the tax applies to, and the tax authority who receives the tax based on CCH tax data.
- Appendices
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Compiling Pricing Plans

When you compile a pricing plan, a pricing XML configuration file is generated from all pricing items and policy items in the pricing domain. The pricing XML configuration file can be generated as a standalone file during pricing validation or as part of a ZIP archive that contains the following additional files:

errors.txt — Error messages generated during the compilation.
data folder — The individual pricing/policy items used to compile the pricing configuration file.

The standalone pricing XML configuration file is considered a development version. It is based off of all files in the workspace of the user validating the pricing, and includes any files that have not been committed to SVN (local modifications known only to this workspace). These files might be in a transitional state and therefore not ready for publishing. In addition, unless the person compiling the pricing has performed an SVN update, the development version might not contain the latest updates from other users' workspaces. For example, if User A deletes a product offer and commits the change to the pricing repository and User B runs get_pricing.py without first updating his or her workspace, the file deleted by User A is still included in the configuration file and not removed from the pricing database when the configuration file is loaded.

The ZIP archive can also be compiled as a development version or a production version. The development version is based off of the files in the user's local workspace and can contain changes that have not been checked in to the pricing repository. The production version is based off of the latest revisions of the pricing files checked in to the pricing repository.

Before compiling a pricing plan, the person compiling the pricing plan should make certain all users have checked in their changes to SVN if the changes should be included in the compilation.