Analyzing Measurement Concept Instances and Their Lifecycle

Objective

After completing this lesson, you will be able to analyze the various types of measurement concept instances and their corresponding lifecycles.

Instance Creation

Let's take a look at instances of the Measurement concept and their lifecycle.

There are several examples when an instance is created:

  • Building houses
  • Building solar farms
  • Building wind parks

Instance Creation Process

Let's have a look into the process to create a Measurement Concept Instance.As an example, the creation of a MC instance could be triggered by a service request from a DSO system by calling the MCM POST API. The MCM cloud sends a corresponding event to the SAP S/4HANA backend which then starts the process to create the location identifiers, meaning the metering locations (technical locations) and market locations (commercial locations).Afterwards the MCM Cloud validates the newly created locations/point of deliveries. The next process on the SAP S/4HANA side is triggered in which the received MC instance data is checked and validated if all metering and market locations have an valid ID. Once the MCM Cloud has performed further checks, an event is being raised which leads to the creation of technical master data for locations: In the SAP S/4HANA backend the connection object, the premise and the device locations are being created.The MCM Cloud continues with the validation of this technical master data. Then, in the SAP S/4HANA backend the utility installation, the location relationships, the supply scenario and the devices are being created.

The image is a flow diagram that describes the process of handling a service request. The diagram has several stages, including creating a measurement concept instance, validating locations and event identifiers, performing checks, creating technical master data, and creating utility installations and location relationships. The process involves various sub-processes and checks to ensure the accuracy and completeness of the service request.

Note

There is the option to include Customer Extension Steps in each of the yellow marked processes on the SAP S/4HANA side to enhance the process to your needs.

In addition the SAP S/4HANA backend creates calculation formula, device info record installations and the profile header and allocation. Load Profile are being assigned and the real-time pricing (RTP) interface is being activated.

The MCM Cloud validated the technical master data so that the SAP S/4HANA backend can continue with the creation of business related master data.This means that the business partner is determined, the premise owner is allocated and the contract account is being created or determined.After the move-in is done, the SAP S/4HANA backend creates the installation facts and the master data for the actors (such as solar panel, wallbox, heat pump etc).

Depending on the country there can be specific subprocesses.Last by not least the MCM Cloud validated the business master data and on the SAP S/4HANA side, the MC Instance data is checked a last time.Finally the MC Instance is set to "final".

The image is a workflow diagram depicting the steps involved in the process of creating and validating a technical master data, event device, and business master data, as well as the finalization and customer extension steps. The diagram includes various sub-processes such as creating calculation formulas, device info records, profile header and allocation, premise owner allocation, contract account determination, and country-specific subprocess. The process also involves validation, activation, and data creation steps.

Note

There is the option to include Customer Extension Steps in each of the yellow marked processes on the SAP S/4HANA side to enhance the process to your needs.

Instance Change

There are several examples when an instance is changed:

  • Extending existing buildings (with standard consumption) by a solar panel, a heat pump, a wallbox or/and a battery storage
  • Partial removal of assets s.a. a solar panel, a heat pump, a wallbox, a battery storage
  • Exchanging assets? In case domain data is changes for example solar panel power range changes; In case properties/process data of the asset change? For example solar panel installed power etc?
  • Exchanging meters?
  • Change of commercial model? → formula changes..
  • Change the metering procedure of (at least) one metering location

One example for an instance change is the move from standard consumption to installing a solar panel which feeds in produced energy into the grid.

The image shows a diagram of a building with various components connected. It includes a cost meter, a heater, and a product. The components are connected by arrows, indicating a flow or relationship between them.
The image depicts a diagram of an energy measurement and distribution system. It shows a Grid Measurement component that measures the active energy, and a Generator Measurement component that measures the active energy of a solar panel. These measurements are connected to two consumer apartments, with the Grid Measurement data flowing to the consumers. The diagram also includes icons representing the Grid and the Solar Panel.

Compared to the standard consumption use case, there is a new asset installed: the solar panel.

In addition, there is an additional meter installed to measure the electricity which is produced by the solar panel.The one-directional meter for the grid-measurement in being exchanged by a bi-directional meter.

From Standard consumption…

The image shows a SAP Measurement Concept Instance screen, displaying information about a Standard Consumption with MMD/RLM/IMS instance. It includes details about the Point of Delivery, Connection Object, Premise, and Installation. The instance is in a Historic status and was valid from 04.03.2022 to 24.03.2022. The screen also provides options to switch to the Metering Location Perspective.

…to Energy Feed-in

The image displays a SAP Measurement Concept Instance screen for a Standard Feed-In instance, which is currently in an Active status. The instance is valid from 25.03.2022 to 31.12.9999. The screen shows details about the Point of Delivery, Connection Object, Premise, and Installation for multiple measurement locations, including MVB1 (Marketlocation Supply), Z1 (Grid Access Measurement), MGEN (Marketlocation Generation), Z1 (Grid Access Measurement), and Z2 (Generator Measurement). The user can switch to the Metering Location Perspective.

Instance Change Process

The image is a workflow diagram that illustrates the process of managing measurement concept instances. The process includes steps such as changing the measurement concept instance, creating or changing locations, verifying location identifiers, checking received measurement data, creating connection objects, creating device locations, and various other sub-processes. The diagram also includes steps for validating locations, creating technical master data, and finalizing the process.
The image depicts a workflow diagram for managing device installations and technical master data. It includes steps such as validating device installation, event device confirmation, validating business data, finalizing the instance, checking received data, and updating local instance to historic. The process also involves creating calculation formulas, utility installation, profile and load adjustments, contract account determination, and country-specific subprocesses. The diagram shows various interconnected stages and decision points in the overall workflow.

Note

There is the option to include "Customer Extension Steps" in each of the yellow marked processes on the SAP S/4HANA side to enhance the process to your needs.

Instance Shutdown

An instance shutdown takes place when the building, the solar or wind park is teardowned.

The image depicts a workflow diagram for managing the shutdown of a measurement concept instance. The process includes steps such as shutting down the measurement concept instance, validating the device removal, validating business data, finalizing the shutdown, and checking received data. The diagram also shows various sub-processes related to removing devices, terminating load profiles, storing premise owner information, and updating installation facts. The overall workflow is divided into sections for Shutdown Measurement Concept Instance, SAP S/4HANA, and Shutdown Measurement Instance.

Note

There is the option to include Customer Extension Steps in each of the yellow marked processes on the SAP S/4HANA side to enhance the process to your needs.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn