Understanding the Energy Data Management Components

Energy Data Management is a solution that fulfills requirements by offering interval reading, settlement of energy quantities, scheduling, and billing of interval energy consumption.

The Energy Data Management (SAP IS-U-EDM) component is fully integrated into the SAP IS-U system and can be installed in an existing SAP IS-U system as a new component. SAP IS-U-EDM is also integrated into Intercompany Data Exchange (SAP IS-U-IDE). This component allows for data exchange in standardized formats and enables the integration of cross-company business processes. SAP IS-U-EDM allows you to bill profiles in SAP IS-U. Profiles are prepared in SAP IS-U-EDM and transferred to SAP IS-U billing via an internal interface. This allows you to bill new types of contracts, such as spot purchases.

SAP IS-U-EDM also interfaces with automated meter reading systems.

Energy Data Management covers the following areas:

EDM is a fully integrated component of SAP S/4HANA Utilities. That means you can manage all energy data imported from both internal and external enterprises, such as load shapes and profiles, for individual points of delivery in one central database or just getting them from an external data base. The data can be validated before processing and exporting it to other components, such as billing.

Energy data can be imported to the EDM Repository from Office applications, such as Excel, using the OLE interface, from AMR systems using BAPIs, from other external systems using IDocs, SOA, IDE, or any service available in BTP.

The profile information can be passed to Billing via the internal RTP interface. For other modules like Customer Service, Customer Experience, SAP Business Data Cloud, and so on, profile data can be sent using internal interfaces, extractors and APIs.

The following image shows deregulation data objects:

Point of delivery is the point to which a utility service is supplied, or for which a utility service can be determined. A point of delivery has an external identifier, a unique number or fixed code, called a point of delivery ID. Note that this will be covered in detail in this unit.

A point of delivery services two roles:

• Electronic data communication during automatic data exchange (deregulation role)
• Exchange of meter reading results (technical role)

Multiple services can be linked to a point of delivery. Note the following points:

• Service: A service that is rendered by a service provider at a point of delivery
  Note

  A point of delivery service is non-billable. A contract is a billable service.
• Service provider: A company that provides a service to a point of delivery

Profile:Time series data that contains values such as consumption or prices for a certain period

Synthetic profile: Profile containing values generated on the basis of predefined periods (defined by day and season groups) and corresponding day and annual profiles. Synthetic profiles are used for classifying customers and customer groups (Refer to the section on Synthetic Profiles).

A point of delivery (PoD) is the point to which a utility service is supplied, or for which a utility service can be determined.

A point of delivery is identified by means of a unique key (point of delivery ID).

• Information about the service supplied to a point of delivery can be provided, even if a change of supplier takes place
• It is relevant to all processes in the deregulated environment (numerous methods for BOR object ISUPOD)

An internal point of delivery ID is always generated when a point of delivery is created. The PoD ID is not visible to the user. If you now select an external point of delivery ID or no point of delivery ID, table EUITRANS creates a connection between the internal and the external point of delivery.

Examples of points of delivery include the following:

• A point between generation and the transmission grid
• The transition point between the transmission grid of one control area and the transmission grid of another
• Any intermediate measurement point (a transformer, for example)
• Point into a customer's installation (premise)

You can use SAP enhancement ISU_EDM_POD_CUSTOMER (BAdI) to create customer-specific fields and display them on a special subscreen in the point of delivery.

Various change documents were updated for the point of delivery. You can display the changes in the point of delivery transactions by choosing Extras→Change Documents in the menu.

A point of delivery can have one of the following roles:

• Deregulation PoD
• Technical PoD

This refers to communication between different utility companies in a deregulated energy market. This can be, for example, the exchange of consumption information between a distribution company and a supplier. A distribution company has measured the consumption (for example, customer's consumption in an installation) for a point of delivery and uses the point of delivery ID to send this information to the customer's supplier. The supplier then bills the customer based on the consumption data.

This refers to communication by means of an automated meter reading system (AMR), for example. This type of communication is used in the Energy Data Management component (SAP IS-U-EDM) for importing profile values. An automated meter reading system uses the point of delivery ID (and the register code of the register) to send information on the measured load shape to IS-U-EDM.

There are two types of PoD:

• Standard point of delivery:

  A PoD with a physical representation in the energy network.

• Virtual point of deliver
  • Represents a point of delivery that summarizes or compresses energy data (for example, for billing company codes)
  • Allocated at installation level.
  • Groups together several standard point of delivery categories.

This is a service that is rendered by a service provider at a point of delivery. A PoD service is a non-billable service used only for information purposes, for example, meter reading.

All services are allocated to a service type and a service provider.

Device 4711, containing the registers listed below, is allocated to installation 0815:

During creation of installation 0815, deregulation point of delivery ZP081501 was created automatically. Allocate a point of delivery ID to the point of delivery so that you have the following allocation:

You can now use the point of delivery ID of ZP081501 and the corresponding register code to import the profile values for the profiles allocated to the registers.

It is not imperative that you use a technical point of delivery to import profile values.

The default role category is Measurement. If you do not specify a role category, as shown in the diagram, profile values are imported for the profile that is allocated to the register with register code Active Energy and the role Consumption.

However, if you want to import profile values to the profile that is allocated to the register with register code Active Energy and profile role Forecast, you must first choose role category Forecast.

A prerequisite for using a deregulation point of delivery for profile value import is that the system from which you intend to import the data uses the same market-standard point of delivery ID as IS- U-EDM.

If this is not the case (for example, because the automated meter reading system from which the values are imported uses its own number), you must use a technical point of delivery to enable profile values to be imported from the AMR.

However, you still need the deregulation point of delivery in order to send data to other market participants within the deregulated energy market. Therefore, communication in the deregulated market continues to occur using the deregulation point of delivery.

Device 4712, containing the registers listed below, is allocated to installation 0816:

In the installation, register REG3 performs the same meter reading tasks as register REG1. For this reason, the same register code is used for identification purposes.

The measurement task described in the register code for the registers allocated to the point of delivery must be unique. However, the allocation is not unique in the following graphic.

If you want to import profile values to the profile that is allocated to the register with register code Active Energy and profile role Measurement, two profiles would come into question.

The load shapes for registers REG1 and REG3 cannot be imported via the same point of delivery. Therefore, it is necessary to use of technical points of delivery for the profile value import.

Point of delivery POD 1 is used to import load shapes for registers REG1 and REG2. Point of delivery POD 2 is used for register REG2.

Point of delivery POD 1 is still used for communication in the deregulated energy market. You must therefore define POD 1 as both a technical and a deregulation point of delivery.

The role of technical point of delivery has a higher priority than the role of deregulation point of delivery. As soon as a technical point of delivery is created, the system uses it for selection purposes.

Note that in this case, allocation at register level (REG1 and REG2) is also necessary for PoD 1 allocated at installation level.

A profile contains values such as consumption and prices for a certain period. Within EDM, a profile is composed of header data and profile values.

The following data is stored within a profile:

• Historical data: Actual (measured) meter readings
• Forecast data: Estimated energy consumption or forecast for a customer's future usage
• Plan data: Proposed energy to be consumed by each supplier (aggregation of forecast and/or historical data)
• Conversion factor profile (such as gas law deviation factor)
• Time series, price, temperature, and so on

The profile has the following characteristics:

• Interval length (5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes, 1 day, and so on)
• Unit of measurement (kWh, kW, price, temperature, factors, and so on)

The following are examples of interval data:

• Values measured by an interval meter every 15 minutes
• Values forecasted for an interval meter every 60 minutes
• A price index from the energy exchange with an hourly amount

The time-of-use prices (TOU prices) for electricity are based on electricity costs during a particular period of time. TOU rates are, for example, divided into three time blocks for every twenty- four hour period (on-peak, mid-peak, off-peak) and by seasons of the year (summer and winter).

In a TOU rate structure, higher prices are charged during utility peak-load times. Such rates can provide an incentive for consumers to curb power use during peak times.

The RTP interface handles the following:

• Determination of consumption blocks
• Determination of peak values (for example, maximum demand)

TOU pricing is based on complex time-of-use rate structures which are dependent upon the following:

• Seasons - summer/winter
• Day types - working day, public holiday, weekend day
• Time of the day - on/off-peak times

Time-of-use includes:

• Consumption aggregation in every period/time block
• Price calculation for the quantities

The following image illustrates TOU (Time of Use) billing for three different quantities:

The following image illustrates real-time pricing

Real-time pricing is the pricing of energy based on the cost of the energy available for use at the time the it is demanded by the customer.

• New deregulated energy market rules make prices volatile
• Complex rate structures require prices to be able to change at up to hourly intervals

The following applies to real-time pricing:

• Demand and consumption amounts are dependent on each other within each interval. Each interval is valuated separately
• As the price is subject to change, in extreme cases, it can change in every interval

The following image illustrates RTP billing:

The following image illustrates a combination of RTP billing and TOU billing:

The following image illustrates SPOT pricing:

Spot price is the current market price at which short-term energy purchases or sales are made.

• In a regulated market, the price of energy is dependent on:
  • Energy consumption
  • Demand
  • Voltage, pressure, or additional services
• In a deregulated market, the price of energy is dependent on:
  • Consumption patterns over time
  • Accurate forecasting:

    Energy price is dependent on customers' willingness to take risks (hedging)

Energy price is the result of consumption, demand, consumption patterns over time, hedging the price risk, and so on.

Profile header defines the characteristics of profiles:

• Division: Company-internal key for the division category that is predefined by the SAP S/4HANA UTILITIES component.
• Status:
  • This defines the status of the profile based on the SAP standard status.
  • The different kinds of current status include: Active/Usable, Inactive, Allocated/Deletion Flag Set.
  • The user can also set a user status.

The Profile type describes the type of data stored in the profile. It can be adjusted to meet the requirements of the business process.

• They characterize the profile type.
• They are predefined by SAP.
• They are not customizable.

There are five predefined profile types:

• Elementary profile: Contains values that are imported or entered manually
• Synthetic profile: Contains values that are created for a customer group. These values can be grouped together by season, time of day, or day type.
• Formula profile: Contains values that are calculated using a predefined formula and other profiles. You can use a formula profile to calculate the energy-feeding curve of the grid, for example.
• Day profile: Contains values entered at identical intervals and that together describe one day. Day profiles are allocated to synthetic profiles and reproduce the consumption of one day, such as a weekend day in summer or a weekday in winter.
• Integral profile: Only used internally within the system (for performance reasons).

The profile types are provided in initial customizing (historical, forecast, and so on). Further profile types can be customized by the customer.

The following table shows examples of profile types and the corresponding categories:

• Validity date: Date from/to which the profile is valid.
• Date until which profile values were archived: This field contains the date up to which archiving has occurred.
• A day offset can occur with synthetic profiles and elementary profiles (for example, gas day as of 06:00).
• Creation Options: If you have activated the Advanced Metering Infrastructure 2 business function (ISU_AMI_2), also make the settings in the Creation Options group frame by choosing a combination of Storage Location of Original Profile Values and the Profile Can be Billed with TOU Interface selection field.

You use the Storage Location of Original Profile Values to specify where the original profile values are stored. The following storage locations are possible:

Profile values originate from EDM: The original profile values are stored in EDM. This is standard for normal interval readings. You can perform all the checks and replacement value procedures that can be performed in EDM.

Profile values originate from an external system; copy in EDM: The profile values originate from an external system. The profile values from the external system are copied into EDM.

Profile values originate from an external system: The profile values originate from an external system. Only the profile header (the definition of the profile) is stored in EDM, the profile values are not managed in EDM.

You can use the Not TOU-Billable and TOU Billable selection fields to specify whether the profile can be billed using a time-of-use interface. This selection field controls the type of billing for profiles that you allocate to an interval meter with the role category, Measurement.

If you select Not TOU-Billable, you can only execute billing using an RTP interface.

If you select TOU Billable, you can execute billing using an RTP interface or a time-of-use interface.

The selected combination from Storage Location of Original Profile Values and the selection field Profile Billable with TOU Interface has the following influence on the other characteristics of the profile:

You can only allocate consistency check groups and replacement value procedure groups in the profile header if you have chosen the combination: Storage location Profile Values Originate from EDM and the selection field Not TOU Billable (see table, combination with X).

With any other combination, you cannot allocate consistency check groups and replacement value procedure groups (see table, combination with 0).

• Profile value category: Determines the category of the profile values. This includes amount, factor, quantity, demand, price, and others.
• Interval length: Interval between two values in a profile (for example 5, 10, 15, 30, 60 minutes, 1 day)
• Currency: Specifies the currency for the profile values (for example, Euro or US Dollar for a price profile)
• Unit of measurement for meter reading: Unit of measurement for the values (kW, kWh, MWh, and so on)
• Decimal places: Number of decimal places defined for the profile values
• Cumulative values: Indicates that at a time, t, the value is dependent of the values of t-n. Generally, this is not the case with an interval meter.

The following image shows cumulative values:

The Cumulative Values Checkbox on the profile header is used in the following manner:

• If checked, the meter read value for each interval is added to the previous intervals measured value (as shown above in the first example).
• If not checked, the meter value is the same as the value displayed in EDM (typical for interval meters).

Once you have saved the profile header, you cannot make any changes other than to the name of the profile, the consistency check groups, and the replacement value procedure groups.

BAdI ISU_EDM_PROFHEAD enables you to add a tab page with your own enhancements to the profile header.

Profile types are defined and allocated to a profile category in Customizing. The Customizing path is as follows:

• Define Profile Types
  • Description (free choice of text to describe the profile type)
  • Profile category (elementary profile, synthetic profile, formula profile, day profile)
  • History (historical profile, schedule profile, forecast profile) - used for information purposes only
  • Number range number
• Define permissibility of interval lengths per profile type:

  For each new profile type, define the permitted interval lengths (5, 19, 15, 30, 60 minutes, 1 day)

Details within the profile header can be maintained for the synthetic and formula profiles.

The system automatically assigns a profile number if you have already defined number ranges for profile categories in Customizing.

Customizing path:

You can use the master data generator (master data template EDM_PROFHEAD) to create and change profile headers for elementary, day and form profiles, and to create and change formula allocations for the formula profile calculations.

The role determines which task the profile carries out at the register or installation.

Profile roles are used for the following:

• Importing and exporting profile values
• The profile whose values are to be processed is identified using the point of delivery, the register code, the profile role, and the role category
• In real-time pricing (RTP) billing, roles enable the flexible allocation of profiles to input parameters on the RTP interface.
• In the RTP rate, the role replaces the function of the register operand as the source of the consumption data.
• In replacement value creation, the role determines the reference profile.
• In settlement, roles are needed to identify settlement parameters.

In Customizing, you can determine for each individual role (regardless of the category), whether the profile allocated using this role can be changed after billing has taken place (changes to profile values and profile allocation).

The role is used to allocate the profile to the register in time slices.

For example: A customer (this means the register) is initially allocated profile 101 using the role, Consumption Measured.

The following are example profile roles provided as standard in Customizing:

• Consumption measured
• Consumption forecast
• Agreed demand
• Price profile
• Agreed consumption

  On-peak rate

• Agreed consumption

  Off-peak rate

• You can define other profile roles in Customizing.

Roles: These refer to the profile from which values are to be used.

Some roles are defined by SAP. You can define further roles in Customizing:

There are four role categories predefined by SAP:

• Measurement: Profiles with this role category describe consumption measured by an interval meter. You can only allocate one profile with this role category to a register. When profile values are imported using the point of delivery and its register code, this role category is used to identify the profile into which these values are to be imported (default is role category Measurement).
• Forecast: Profiles allocated to this role category describe the consumption forecast for the interval meter. You can only allocate one profile with this role category to a register of an interval meter. The frequency of the roles in this category must always be 1. The forecast is used by the transmission system operator (TSO) for the procurement schedule.
• Settlement: Profiles allocated to this role category are included in the settlement process. You can only allocate one profile with this role category to a register or an installation.
• Not specified: Use this category for roles with unspecified functions.

You can define roles and allocate them to role categories defined by SAP.

In Customizing below, choose:

• Role: ID for the role of a profile allocation
• Role description: Text describing the role of a profile allocation
• Frequency (frequency of allocation per role): Number that indicates how often a profile with a certain role can be allocated to a register of an interval meter. You must specify 1 for the frequency of roles in role category Measurement and Forecast.
• Role category: Category to which the role is allocated

There are two system views by which the profile can be allocated:

• Register view: Search by any of the following to drill down to the register:
  • Business partner
  • Contract account
  • Contract
  • Installation

  Note that in the profile view, the profile data is shown in the upper right side of the screen.

• Profile view: Search by the profile that you want to allocate

  Note that in the register view, the register data is shown in the upper right side of the screen.

When changing devices, the profile allocation remains the same.