Utilizing Deregulation Data

Objective

After completing this lesson, you will be able to describe the purpose and usage of the Point of Delivery

Deregulation Data – Introduction

Key requirements in a deregulated market: unbundling of companies; mapping market participants and relationships; mapping cross-company processes; support of exchange standards; settlement.
Diagram of market participants showing interconnected roles between suppliers, distributors, and a settlement coordinator to illustrate energy supply and distribution relationships.
  • A simplified form of deregulated market: independent companies supplying customers in different grid areas.
  • A settlement coordinator ensures that settlement is cleared.
A visual representation of relationships and data flow between energy market participants, including suppliers, distributors, coordinators, and service providers.
  • Increased complexity resulting from additional market participants:
  • Deregulation also in other areas, for example the meter reading service. However, these services are usually no longer chosen by the customer but by the supplier.
Illustration of supply chain communication flow among suppliers and distributors, highlighting interconnected relationships and the directional exchange of information or goods.
  • Deregulation means that market participants need to communicate more intensively.
  • This is particularly important as a result of new cross-company processes.
  • Communication can take place directly between all the market participants involved. This can only function properly if strict market rules are defined, determining who communicates at what time with whom and which data they exchange.
Illustration highlighting centralized communication flows between suppliers, distributors, and a clearing house, emphasizing streamlined coordination among involved parties.
  • Alternatively, market participants can always communicate through the medium of an independent authority, often state-controlled, also termed a "clearing house".
  • This procedure simplifies communication processes for the other market participants.
A simplified depiction of energy market processes showing roles of distributor, supplier, and customer exchanging services, billing, and data through electronic communication.
  • Simplified model showing only the distributor, supplier, and customer.
  • The deregulated market has a number of new cross-company business processes that necessitate data exchange between companies.
  • In addition to the central processes for a change of supplier and for payment processing, the following business processes are typical: notifications of meter reading and consumption information, changes of customer data, and requests for services from the distributor, for example a replacement as a result of a customer complaint.
Visual representation of SAP S/4HANA Utilities data model illustrating interconnected entities like service providers, contracts, premises, and delivery points for streamlined operations.
Diagram illustrating SAP S/4HANA Utilities data model flow, emphasizing the central Point of delivery connecting service providers, contracts, installations, and profile management systems.
Graphic explaining the Point of Delivery concept, highlighting its role in utility service identification, deregulation processes, and integration with technology systems.
  • Deregulation point of delivery

    This type of point of delivery is assigned by distributors or regulatory entities to clearly define the point of energy supply when communicating with retailers or service providers. It is allocated to one installation and one installation can be allocated to only one PoD. However, one PoD can be allocated to several installations. This is the case when two installations with the same PoD are required for billing a supply or distribution contract, for example. These installations must have the same division and be assigned to the same premise.

  • Typically the deregulation point of delivery value is defined by the distributor since they own the service location data.
  • Technical point of delivery

    In this case, registers are allocated to a point of delivery. This type of PoD is especially useful for the Energy Data Management (EDM) component. The PoD is used for identifying profiles that are allocated to registers in EDM. In EDM, the PoD is specified when profile values (load shapes) are imported. The interval meters allocated to the PoD can then be calculated automatically. Profile values are then transferred to the profile allocated to the interval meter. This allows you to import load shapes without information on the objects managed in EDM. You only require the point of delivery ID. This allows you to easily import load shapes from an automated meter reading system, for example.

Diagram illustrating key components connected to the concept of Point of Delivery, emphasizing data management, allocation, services, exchanges, and operational scenarios.
  • Settlement: the point of delivery is necessary when allocating consumption to settlement units. The allocation of a point of delivery (and its consumption) to a settlement unit is determined by the PoD services allocated to the PoD. A PoD service can also be a billable service in the form of a contract.
  • Only the deregulation point of delivery is significant in intercompany data exchange.
  • A supply scenario describes the environment of the past, current, or future supply situation for a point of delivery. The supply scenario refers to the description of the market participants and their roles (such as supplier, transmission company, distributor) and the master data in the SAP S/4HANA Utilities system (such as service type, single or dual contract model). This means, for example, that the supply scenario provides information on those involved in supply and who performs which services for the point of delivery.
Illustration of interconnected entities in a utility data model, emphasizing relationships between service providers, grids, delivery points, contracts, installations, and profiles.
Illustration of energy flow and coordination, showing connections between the grid, service providers, regional structures, and delivery endpoints for efficient distribution.

Grid: Object in the SAP S/4HANA Utilities system that corresponds to a distributor's grid or part of it.

You can manage grids for a distributor. You can split a distributor's grid into several smaller grids for the following reasons:

  • You want to map grid hierarchies in the system
  • The distributor's grid covers several control areas
  • The distributor's grid is divided into different levels (for example, voltage levels or pressure levels), which you want to map in the system as separate grids

It is even possible to allocate different grids (and therefore different distributors) for different voltage levels to points of delivery for a connection object (for example, one postal address) that has several points of delivery.

  • You can store default values for the grids in the postal regional structure.
Illustrates a power grid hierarchy from high to local voltage levels, connecting regional areas and enabling distribution to end users, emphasizing structure and energy flow.
  • You can map grid hierarchies in the system by specifying a higher-level grid for a grid. These hierarchies can be evaluated during schedule creation, so as to compile total schedules for the different grids.
  • The following relationships can exist between a point of delivery and a grid:

    A point of delivery can be assigned a grid as an attribute. In this case, the point of delivery is usually a physical device. This means it is possible to perform separate settlements for individual grids in Energy Data Management.

  • By assigning a virtual point of delivery to a grid, you can store settlement results for each grid in Energy Data Management.
Diagram showing key roles of a service provider, including managing processes and connecting market participants, with tasks like contracts, installation, data, and communication.
Illustration explaining service provider processes, emphasizing agreements, historical data, and electronic data exchange between distributors and suppliers to streamline operations.
Visual representation of SAP S/4HANA utilities data model, emphasizing interconnected entities like contracts, service providers, delivery points, and business structures.
Overview of key contract terms and roles in deregulated environments, highlighting service provider responsibilities, invoicing, external references, and customization processes.
  • Service provider

    A service provider can be either an external company or an organization within your own company. Service providers always offer only type of service (energy supply, energy distribution, meter reading service, and so on). Companies that provide many types of services can be stored in the system a number of times as different service providers. In data exchange in the deregulated energy market, the service provider performs the function of the data sender or receiver.

  • Deregulation scenarios

    The deregulation scenario is determined by the combination of fields in the installation, contract, and service. Examples of deregulation scenarios are as follows:

    • The customer receives a bill from distributor and supplier.
    • The customer receives only one bill from the distributor. The supplier's charges are also printed on this bill (rate-ready billing).
    • The customer receives only one bill from the supplier. The charges for grid usage are printed on this bill too (sole provider).
Diagram depicting relationships in SAP S/4HANA utilities model, emphasizing installation as the central node connecting services, contracts, profiles, and regional infrastructure.
Graphic explaining key fields in deregulated energy installation management, focusing on services, billing, statuses, supply, and delivery, with customization options highlighted.
  • Service type

    The service type describes a utility service provided to the customer in a deregulated market (such as energy distribution or supply, or device management). Service providers are always defined for exactly one service type.

    You can define any number of service types. A service type is allocated to a service category. In SAP S/4HANA Utilities, each premise can only have one installation with the service role Distributor and one installation with the service role Supplier. This means that one premise can contain not only one distributor and one supplier installation, but also any number of installations with a service type to which no service role has been allocated.

  • The billing service provider determines which service provider bills the contracts. Historical changes are taken into account in so far as the valid service providers are determined at the end of the billing period.
  • Deregulation status

    Deregulation includes a number of statuses, from Released to Deregulated. Once a customer has reached a certain status, they can be supplied by other suppliers. You must store all deregulation statuses here. A customer cannot be supplied by another supplier until the Enrollment possible field has been set in Customizing.

A visual representation of service relationships in SAP S/4HANA Utilities, highlighting connections between service providers, delivery points, contracts, and system components.
Illustrates relationships between service providers, energy services, and points of delivery in a liberalized energy market, highlighting player roles and service modeling.
Flowchart illustrating relationships between service providers, billable and non-billable services, business partners, contracts, installations, and points of delivery in a service framework.

Different services can be allocated to one point of delivery. Services to be billed are contained in contracts.

Overview of delivery service points emphasizing their role in information sharing, settlement processes, and automated creation, visually reinforced with a globe and home icons.
Diagram explaining a service provider agreement, showing collaboration between a market partner and a processing service provider to define process parameters.
  • The market partner can be a third party service provider (one not managed in your own system) or a service provider of your own.
  • Processing service provider: service provider for whom a service provider agreement is defined (own service provider – in own system).
Diagram illustrating key capabilities of a Supply Scenario tool, emphasizing adaptability, custom integration, enhanced data management, and support for regulatory processes.

A supply scenario describes the environment of the past, current, or future supply situation for a point of delivery. The supply scenario refers to the description of the market participants and their roles (such as supplier, transmission company, distributor) and the master data in the SAP S/4HANA Utilities system (such as service type, single or dual contract model). This means, for example, that the supply scenario provides information on those involved in supply and who performs which services for the point of delivery.

A chart illustrating energy usage patterns that vary by season, days of the week, and specific profiles for weekends and workdays, highlighting weekday-weekend contrasts.
  • A synthetic profile represents a customer/customer group's consumption pattern and is allocated to the installation. The consumption factor allows you to take a specific customer's consumption behavior into account.
  • Values for synthetic profiles are defined using reference measurements or statistical methods and stored as day profiles in the Energy Data Repository.
  • The structure of the synthetic profile is determined according to the allocation of season, day, and time-of-use groups.
  • When the synthetic profile is generated, the day profiles (standard load profiles) are determined according to the hierarchy. The profile values for the day types are then transferred to the synthetic profile in accordance with the hierarchy settings.
A daily energy usage profile showing consistent patterns with a single error spike disrupting expected consumption trends over time.
  • What is a profile?

    • Contains values such as consumption and prices for a certain period.

    • A profile in EDM comprises header data and profile values.

  • The following data is stored in a profile:

    • Historical data: actual (measured) meter readings

    • Forecast data: estimated energy consumption or forecast of a customer's future usage

    • Planning data: proposed energy consumption per supplier (summary of forecast and/or historical data)

    • Conversion factor profile (for example, gas law deviation factor)

    • Rate/price/temperature profile

    • Characteristics of a profile
      • Interval lengths (5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes)
      • Unit of measurement (kWh, kW, price, temperature, factors, etc.)
    • Examples of interval data:
      • Values measured by an interval meter every 15 minutes
      • Values forecast for an interval meter every 60 minutes
      • Price index from the energy exchange with an amount per hour
Illustration of two connected systems highlighting processes, interaction centers, and data exchange (IDE) between separate entities for managing distribution and operations.

The above diagram depicts a scenario in which two separate companies (distributor and supplier) are mapped in different clients or systems. This means that contracts C1 (grid) and C2 (delivery) are also recorded in separate systems. Communication between the two systems, as well as with external systems, is made possible by the IDE component of SAP S/4HANA Utilities.

Illustration of interconnected business processes and systems demonstrating integration between contracts, distribution, and interaction centers in a unified operational framework.

The above diagram depicts a scenario in which two separate companies (distributor and supplier) are mapped in the same system. The two companies are separated by being allocated different company codes. This means that contracts C1 (grid) and C2 (delivery) are both recorded in the same system with different company codes (CCd 0001 and CCd 0002). Communication with external systems is made possible by the IDE component of SAP S/4HANA Utilities.

Deregulation Master Data

Business Example

Task 1:

Name five new master data objects that were included in the SAP S/4HANA Utilities master data model as part of deregulation.

Steps

  1. Name five new master data objects that were added to the SAP S/4HANA Utilities master data model as part of the new deregulation functions.

    1. Grid

    2. Service

    3. Service provider

    4. Device info record

    5. Point of delivery

Task 2:

Name two roles of points of delivery. List the most important distinguishing features.

Steps

  1. Which two point of delivery roles do you know? What are the most important characteristics differentiating the two roles?

    1. Deregulation point of delivery: When you create an installation, a deregulation point of delivery is automatically generated. Allocation of a point of delivery ID is optional. You can allocate a deregulation point of delivery to one or two installations. If you allocate two installations to the point of delivery (2-contract model), the same devices (such as meters) must also be installed for billing in both installations. Only one deregulation point of delivery can be allocated to an installation. However, the same installation can be allocated to one or more technical points of delivery.

    2. Technical point of delivery Flag a point of delivery as a technical point of delivery in the following cases:

      You need the point of delivery for technical communication with systems that do not work with the point of delivery description commonly used on the market.

      You need the point of delivery for technical communication with systems whose metering system does not correspond to market requirements. For example, if a device meters several points of delivery.

      You can allocate registers (precise logical registers) or installations to a technical point of delivery. Allocation to an installation includes allocation for all registers belonging to that installation. The technical point of delivery is also used for settlement. For example, the aggregated consumption data per settlement unit is linked with the corresponding entity (settlement unit) by a technical point of delivery (virtual role) after the settlement run.

Task 3:

Steps

  1. How can you create a hierarchical grid structure and where do you make the Customizing settings?

    1. You can define a hierarchical grid structure under the following path: SAP Fiori app. On Home page→User Profile icon→App Finder→SAP Menu→Search in SAP Menu, enter Create Grid; Change Grid; Display Grid.

    2. You can now maintain a hierarchy in the HL Grid field. You can make the Customizing settings for grid hierarchies under the following path in the IMG: SAP Fiori app. On Home page→User Profile icon→App Finder→SAP Menu→Search in SAP Menu→Customizing – Execute Project→SAP Reference IMG→SAP Utilities→Tools→System Modifications→User-Defined Enhancements for IDE→Define Grid Level Types.

      The grid level type describes the way in which the grid is subdivided into levels.

      Example:

      For example, the grid level type might be "voltage level". This means the grid is subdivided into different voltage levels.

Task 4:

Steps

  1. Describe the distinction between the terms "service provider agreement" and "supply scenario".

    1. The service provider agreement describes the agreement made between two participating service providers regarding the processes necessary to supply a point of delivery.

      A supply scenario describes the environment of the past, current, or future supply situation for a point of delivery. The supply scenario refers to the description of the market participants and their roles (such as supplier, transmission company, and distributor) and the master data in the SAP S/4HANA Utilities system (such as service type, single or dual contract model). This means, for example, that the supply scenario provides information on those involved in supply and who performs which services for the point of delivery.

Task 5:

Steps

  1. Name two possible contract models that can be defined in the system.

    1. Single-contract model: This means that a contract is created for "delivery" services. An installation is allocated accordingly to this contract. This ensures that both the installation and the contract for the service type "delivery" can be billed (invoiced) and invoiced (contract) for each service type. "Grid usage" and "Settlement coordination" are stored as point of delivery services; that is to say, services that cannot be billed or invoiced. This means that the customer is invoiced for a service and grid usage is billed between the distributor and the supplier.

    2. Dual contract model: This means that separate contracts are created for "grid usage" services and "delivery" services. An installation is allocated accordingly to each of these contracts. This ensures that both the installation and the contract can be billed (invoiced) and invoiced (contract) for each service type. "Settlement coordination" is stored as a point of delivery service; that is to say, a service that cannot be billed or invoiced.

Task 6:

Display the deregulation information for customer US00000926.

Steps

  1. Display the customer environment.

    1. SAP Fiori app. On Home page→User Profile icon→App Finder→SAP Menu→Search in SAP Menu, and enter Data environ. for business partner.

  2. Name the grid to which the customer’s point of delivery is connected.

    1. To which grid does the customer's point of delivery belong? Branch to the installation. The installation contains references to the grid and to the point of delivery. The PoD belongs to gird E-US-GD.

  3. Which distributor and settlement coordinator are involved in supplying the point of delivery?

    1. Which distributors and settlement coordinators are involved in supplying energy to the point of delivery? You can determine the distributor directly from the installation. Switch from the installation to the full screen point of delivery display . On the Supply Scenario tab page, you can view the relevant information regarding suppliers. The distributor for this PoD is "E-US-LD - US Local Distributor" and the settlement coordinator is "E-US-SC - US Settlement Coordinator".

  4. Where can you see the service for which the customer is billed (two options)?

    1. How can you find out which service is provided to the customer? Billable service types are defined in the installation (for example, supply). The service providers are listed in the contract. You can also display the billable services in the supply scenario. You can display the supply scenario from the point of delivery. The contracts displayed represent billable services. A billable service exists for supplier "E-US-LD - US Local Distributor".

Task 7:

Where can you make the settings for data exchange between the individual market participants?

Steps

  1. Give an example from the system.

    1. Where can you make the settings for data exchange between the individual market participants?

      Give an example from the system.

      Display a service provider (SAP Fiori app. On Home page→User Profile icon→App Finder→SAP Menu→Search in SAP Menu and enter Display Service Provider) contains information on the settings for data exchange.

  2. Does this information have a historical validity period?

    1. Yes – valid-from and -to dates specified on the Data Exchange tab indicate the validity period of the data.

  3. Where can this information be overwritten?

Task 8:

Steps

  1. Name the different types of profiles and identify the important characteristics of each.

    1. Standard Profile: Contains values such as consumption and prices for a certain period. A profile in EDM comprises header data and profile values. The following data can be stored in a profile:

      • Historical data: Actual (measured) meter readings
      • Schedule data: Proposed energy to be consumed per supplier (aggregation of forecast and/or historical data)
      • Conversion factor profile (such as gas law deviation factor)
      • Rate/price/temperature profile
      • Characteristics of a profile:
      • Interval lengths (5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes)
      • Unit of measurement (kWh, kW, Price, Temperature, Factors, and so on)
      • Examples of interval data:
      • Values measured by an interval meter every 15 minutes
      • Values forecast for an interval meter every 60 minutes
      • Price index from the energy exchange with an amount per hour

      Synthetic Profile: Profile whose values are generated based on predefined periods (defined using blocks of days and seasons) and the allocated standard profiles. Synthetic profiles are used where an interval measurement does not take place. They are used to classify the consumption patterns of different customer groups. Customers that have similar consumption patterns are assigned the same synthetic profile.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn