The Importance of Understanding Your Market

As noted previously, it is CRITICAL that you have a firm understanding of how your market operates before you begin planning your implementation.

MTM is designed as a configurable framework rather than a market-specific application. Although it provides common processes for enrollment, billing, payments, customer changes, and retailer communications, the business rules governing those processes vary considerably from one market to another.

Many implementation decisions—including customer setup, transaction processing, billing behavior, and registration point design—depend on market requirements rather than product configuration alone.

Successful MTM implementations begin with an understanding of the market's business rules. The application provides the framework for implementing those rules but does not prescribe how every market should operate.

Types of Market Participants

Within most markets there are three primary types of participants:

• Distributor: This is you, the utility implementing MTM US Distribution. In most markets, the Distributors own the transmission system (including substations, transformers, and wires) as well as the meters installed at customer service points.

  Note:

  When defining Billing Options, "We" and "Us" refers to the Distributor. In the system, the Distributor us defined as a Market Participant service provider.
• Retailers: Retailers are organizations that sell electricity to customers. In the system, retailers are defined as Market Participant service providers.

  Note:

  When defining Billing Options, "Them" and "They" refers to Retailers.
• Customers: Customers are the residential and commercial/industrial entities that purchase power from a retailer. In the system Customers are represented by a Registration point.

Note that many markets have other market participants, such as Independent System Operators (ISOs) or Regional Transmissions Organizations (RTOs), but the focus of market transaction messaging for US Distribution is between the Distributor and Retailers.

Why Market Knowledge Matters

Unlike many enterprise applications, MTM does not assume a single business model. Different markets define:

• Customer ownership
• Retailer responsibilities
• Distributor responsibilities
• Billing relationships
• Enrollment procedures
• Transaction timing
• Customer switching rules
• Payment settlement
• Registration point identification

These differences influence almost every aspect of an implementation. For example, one market may require the distributor to create customer records during enrollment, while another assumes the customer already exists. Likewise, some markets require retailer settlement based on customer payment, while others require settlement based on bill due dates. Understanding these differences before implementation helps ensure that the application is configured to support the correct business processes.

Markets Differ in More Than Geography

Markets should not be viewed simply as geographic regions. A market defines the business rules under which distributors, retailers, and customers interact. Those rules determine:

• Which organization owns customer information
• Which organization bills the customer
• Which transactions are exchanged
• When transactions are exchanged
• Which participant is considered the system of record for different types of information

Even distributors operating within the same state may implement different business practices to satisfy their market obligations.

Examples of Market Differences

The following examples illustrate how business rules vary from market to market.

Texas

Texas represents a fully deregulated retail market. Characteristics of this market include:

• Retailers own the customer relationship.
• Customers may switch retailers outside normal billing cycles.
• Enrollment often creates the customer within the distributor's system.
• Retailers generally bill customers directly.
• Market processes emphasize frequent enrollment and switching activity.

PJM and Similar East Coast Markets

Many PJM-style markets operate differently.

Characteristics of these markets include:

• Customers typically already exist within the distributor's customer information system.
• Distributor billing is common.
• Retailer relationships are established without creating new customer records.
• Switching frequently occurs at billing-cycle boundaries.

Limited Deregulation Markets

Some markets support only limited customer choice. For example, some markets:

• Restrict the number of customers that may enroll with retailers.
• Allow retailer enrollment only during defined enrollment periods.
• Require customers to return temporarily to distributor service before enrolling with another retailer.

These markets often require different enrollment and customer lifecycle processing than fully deregulated markets.

Market Rules Affect the Entire Customer Lifecycle

Market requirements influence every stage of the customer lifecycle. The table below outlines how the market rules affect various processes in the customer lifecycle.

Lifecycle Activity	Market Rules Influence
Enrollment	Customer creation, retailer relationships, effective dates
Billing	Billing responsibility, bill-ready or rate-ready processing
Payments	Retailer settlement and receivables processing
Customer Changes	Which participant owns customer information
Retailer Switching	Transaction timing and conflict resolution
Customer Drop	Manual drop processing and move-out behavior

Because each of these processes depends on market rules, understanding those rules should be an early implementation activity.

Configuration Reflects Market Rules

Most MTM configuration exists to represent market behavior rather than application behavior. Examples include:

• Service Provider Configuration
• Billing Relationships
• Registration Point models
• Customer Registration Process implementations
• Validation rules
• Transaction processing
• Completion processing

Configuration should therefore be driven by documented market requirements rather than assumptions based on previous implementations.

Do Not Assume One Market Represents Another

Because market rules can vary so widely, solutions developed for one market should not automatically be applied to another. For example:

• A Texas implementation may rely heavily on customer creation during enrollment, while another market assumes customers already exist.
• Billing and payment processing may differ depending on whether the distributor or retailer bills the customer.
• Registration points may identify a premise, a service point, or a customer at a premise depending on market requirements.

Although the MTM framework supports all of these approaches, each implementation must determine which model is appropriate for its market.

Implementation Guidance

Before configuring MTM:

• Understand the regulatory structure of the market.
• Identify the responsibilities of distributors and retailers.
• Determine who owns customer information.
• Understand the billing model used by the market.
• Identify the registration point model.
• Review enrollment, switching, and drop requirements.
• Understand payment settlement rules.
• Identify any market-specific transaction requirements.

These activities provide the foundation for configuring MTM to support your organization's business processes.