Advanced Metering Infrastructure

Technical documentation of AMI-related use cases supported by SAP S/4HANA

The documentation for the service operations mentioned in the use cases can be accessed from
both the links in the summarizing tables and also from the links at the bottom of this text.

Use Case 1: Device Initialization Process

Before a smart meter can be used, it must be initialized to set up a bidirectional communication between the
smart meter, the MDUS, and SAP for Utilities.

The process starts when a clerk enters a goods receipt for the smart meter in SAP for Utilities, which also creates
the device's master data. At this point, SAP for Utilities sends a request to the MDUS system asking it to create a
representation for the device in its system. This request is sent using the Request Utilities Device Smart Meter
Creation enterprise service, whose business object is Utilities Device. The MDUS sends back a confirmation
message, using the Change Based on Utilities Device Smart Meter Creation Confirmation enterprise service
operation.

Later, when the smart meter is physically installed at the customer site, the MDUS system sends a notification
back to SAP for Utilities using the Change Based on Utilities Device Smart Meter Registered Notification, telling
SAP for Utilities that this meter has been registered in a specific AMI system and that it can now be used for
subsequent processes.

Next, in SAP for Utilities, a clerk technically installs the smart meter. This process, which is known to users of
SAP for Utilities, involves assigning a measurement task to a device. A Utilities Measurement Task indicates why
types of measurements should be taken using this device (for example, measuring consumption, energy, volume,
or power periodically as indicated). It associates the physical meter with this measurement task, which can also
be regarded as a logical representation of the meter's function. Technical installation also includes configuring the
meter in SAP for Utilities, specifying how many registers there are, for example, for measuring energy use during
different time blocks, such as daytime and night time usage. Performing this task in SAP for Utilities invokes a
request to the MDUS, which is executed by the Request Utilities Device Smart Meter Register Creation enterprise
service operation. The MDUS then sends back a confirmation, using the Change Based on Utilities Device Smart
Meter Register Creation Confirmation service operation.

If discrete meter readings are collected instead of interval data, SAP for Utilities sends a request to the MDUS to
collect meter readings. Alternatively, it is possible to enter meter readings manually (the prerequisite for doing so
is the activation of a BAdI) and provide them to MDUS. (For more information, see use case 3).

The device has now been both physically and technically installed; the final step is to install it from a billing
perspective. At this point, the customer has a contract with you and the point of delivery has been assigned to this
customer. SAP for Utilities informs the MDUS that the point of delivery (the customer premises) has been
associated with this specific meter. SAP for Utilities communicates this information by invoking the Notify of Smart
Meter Utilities Measurement Task Point Of Delivery Assigned enterprise service operation.

Note: If multiple devices or measurement tasks are involved, this triggers the corresponding bulk services.

The following table summarizes the steps in this use case and the associated enterprise services:

Step Invoked Enterprise Service Operation

Step 1: Purchase smart meter No enterprise service is invoked in this step

 Step Invoked Enterprise Service Operation

Step 2: Book goods receipt for smart meter

Request Utilities Device Smart Meter Creation
within SAP for Utilities, which sends a
message to MDUS

Step 3: MDUS sends back a confirmation

Change Based on Utilities Device Smart Meter Creation
message
Confirmation

Step 4: Install smart meter at the customer's

Change Based on Utilities Device Smart Meter Registered
site, after which MDUS sends a message
Notification
about the registration of the meter

Step 5: Install smart meter technically in SAP

Request Utilities Device Smart Meter Register Creation
for Utilities, which sends a message to MDUS
(More messages depending on the master data)

Step 6: MDUS sends back a confirmation

Change Based on Utilities Device Smart Meter Register
message
Creation Confirmation

Step 7: Discrete meter readings See use case 3

Option 1: Request meter readings from
MDUS
Option 2: Send meter readings to MDUS

Step 8: Set up smart meter billing in SAP for Notify of Smart Meter Utilities Measurement Task Point Of
Delivery Assigned
Utilities

Use Case 2: Change Technical Master Data

In use case 1, we set up the smart meter so that it functions and reads consumption information for billing the
customer. But even after a meter is installed, a company may decide that they want to change how they measure
their customers' consumption. For example, it may be that initially, total consumption by day was being measured.
Now, however, they want to measure usage in two segments: daytime usage and nighttime usage. These
segments are called registers and the registers are an attribute of the business object Utilities Device.

To change the number of registers, first the change is made in SAP for Utilities, which invokes the enterprise
service Request Utilities Device Smart Meter Register Change is invoked. The MDUS makes the corresponding
change in its metering infrastructure and then sends back a confirmation message: Change Based on Utilities
Device Smart Meter Register Change Confirmation.

Please note: If multiple devices or measurement tasks are involved, this triggers the corresponding bulk services.

The following table summarizes the steps in this use case and the associated enterprise services:
 Step Invoked Enterprise Service Operation

Step 1: Change the number of registers in

Request Utilities Device Smart Meter Register Change
SAP for Utilities, which then informs the
MDUS

Step 2: The MDUS makes the change in the

Change Based on Utilities Device Smart Meter Register
number of registers and sends back a
Change Confirmation
confirmation

Use Case 3: Discrete Meter Reading Process

To bill customers for consumption, you must find out how much energy they have used. Discrete meter readings
are required at specific points in time, for example business-related points in time such as the billing cycle or for
tariff changes, and technical points in time, such as device installation, device removal, and so on.

The discrete meter reading process can be executed in one of two ways:

1. If the meter reading originates from MDUS (remote meter reading, main use case): SAP requests meter reading
results from MDUS.
2. If the meter reading originates from SAP (manual meter reading with entry in SAP, special use case for device
installation/removal): SAP sends meter readings to MDUS.

Use Case 3a: SAP Requests Meter Readings from MDUS

In this use case, the utilities company sends out a bulk request to read all the meters in a particular group
(defined according to your setup) as of a given date, which can be a past or future date.

SAP for Utilities sends out this request to the MDUS by invoking the enterprise service Request Smart Meter
Meter Reading Document Creation as Bulk MDUS then acknowledges the request (this can take up to a day) by
invoking the Change Based on Smart Meter Meter Reading Document Creation Confirmation as Bulk enterprise
service operation. However, this confirmation message is not simply an acknowledgment of the request; it also
includes application level details, such as the fact that a specific point of delivery is not known to the MDUS. In
other words, the MDUS is saying, I will read all the meters except for this one and the one for which I have no
information. (In the best case, all meters are known to the MDUS and no such exceptions occur.)
The MDUS then reads the meters according to the date the read was requested: either as soon as possible (for a
present or past date) or on the specified date (in the case of a future date). The MDUS sends the meter readings
to SAP for Utilities by invoking the Create Meter Reading Document Result as Bulk enterprise service operation,
which uses the Meter Reading Document business object. After SAP for Utilities has uploaded the meter reading
documents, it sends a confirmation message back to the MDUS, invoking the Confirm Meter Reading Document
Result Creation as Bulk enterprise service operation.

The following table summarizes the steps in this use case and the associated enterprise services:

Step Invoked Enterprise Service Operation

Step 1: SAP for Utilities sends a request to Request Smart Meter Meter Reading Document Creation as
MDUS that a group of meters be read as of a Bulk
given date, past or future
 Step Invoked Enterprise Service Operation

Step 2: The MDUS acknowledges the request Change Based on Smart Meter Meter Reading Document
and informs SAP for Utilities of any Creation Confirmation as Bulk
exceptions (meters that do not match its
information)

Step 3: The MDUS performs the readings Create Meter Reading Document Result as Bulk
and sends them to SAP for Utilities

Step 4: SAP for Utilities confirms that it Confirm Meter Reading Document Result Creation as Bulk
received and uploaded the readings

If the request for meter reading (“Meter Reading Order” in SAP’s terminology) is cancelled in SAP, a meter reading is no
longer required. SAP informs MDUS about this cancellation:

Step Invoked Enterprise Service Operation (only

services related to meter reading results; the device
installation process triggers further enterprise services)

Step 5: A cancellation request for the meter Request Smart Meter Meter Reading Document
reading order is sent to MDUS Cancellation or Change Based on Smart Meter Meter
Reading Document Cancellation Confirmation

Step 6: The MDUS acknowledges the request Request Smart Meter Meter Reading Document
and informs SAP for Utilities of any Cancellation as Bulk or Change Based on Smart Meter
exceptions Meter Reading Document Cancellation Confirmation as
Bulk

Use Case 3b: Sending Meter Reading Results from SAP to MDUS
Generally smart meters are read remotely following the process steps in use case 3. There are some situations
where AMI head end systems are not able to capture discrete meter reading results and forward them to MDUS.
These are:

• Installation of smart meters

• Replacement of smart meters
• Removal of smart meters

In such cases, meter reading results manually taken by the service technician are entered in IS-U and then sent
to MDUS. As soon as a meter reading result is communicated to MDUS, changes or cancellations of the meter
reading result also have to be communicated to MDUS to keep data consistent between SAP and MDUS.
The main reason for providing these meter reading results to MDUS is that VEE processing takes place in MDUS.
The meter reading result for device installation is particularly important for validation of subsequent meter reading
results by MDUS.
As a prerequisite for this use case, you must activate the BAdIs ISU_AMI_ATTR_MR and ISU_AMI_SEND_MR.
In the first step, a meter reading result is entered in SAP and communicated to MDUS:
 Step Invoked Enterprise Service Operation (only
services related to meter reading results; device
installation process triggers further enterprise services)

Step 1: Device installation takes place, a Request Smart Meter Meter Reading Document Result
meter reading result is entered in SAP for Creation or Request Smart Meter Meter Reading Document
Utilities and sent to MDUS (create request) Result Creation as Bulk

Step 2: The MDUS acknowledges the request Change Based on Smart Meter Meter Reading Document
and informs SAP for Utilities of any Result Creation Confirmation or Change Based on Smart
exceptions Meter Meter Reading Document Result Creation
Confirmation as Bulk

To keep the must be communicated if they have previously been sent to the MDUS:

Step Invoked Enterprise Service Operation

Step 3: Meter reading result is changed in Request Smart Meter Meter Reading Document Result
SAP for Utilities, the changed meter reading Change or Request Smart Meter Meter Reading Document
result is sent to MDUS (change request) Result Change as Bulk

Step 4: The MDUS acknowledges the request Change Based on Smart Meter Meter Reading Document
and informs SAP for Utilities of any Result Change Confirmation or Change Based on Smart
exceptions Meter Meter Reading Document Result Change
Confirmation as Bulk

The installation / removal / replacement of a device can also be cancelled in SAP for Utilities. In this case, the
meter reading results sent previously related to the device transaction are obsolete and cancelled in SAP for
Utilities. To ensure that data remains consistent, SAP for Utilities sends a cancellation request to MDUS:

Step Invoked Enterprise Service Operation (only

services related to meter reading results; device
installation process triggers further enterprise services)

Step 1: The cancellation request of the meter Request Smart Meter Meter Reading Document
reading document is sent to MDUS Cancellation or Change Based on Smart Meter Meter
Reading Document Cancellation Confirmation

Step 2: The MDUS acknowledges the request Request Smart Meter Meter Reading Document
and informs SAP for Utilities of any Cancellation as Bulk or Change Based on Smart Meter
exceptions Meter Reading Document Cancellation Confirmation as
Bulk
Use Case 4: Reading One Customer's Meter: On Demand Read
A utilities customer is moving out (or changing suppliers), so this transition requires this customer's meter to be
read on a specific date. This use case is very similar to use case 3, but it simply handles one customer as
opposed to a larger number.

SAP for Utilities sends out a request to read the customer's meter on a given date to the MDUS by invoking the
enterprise service Request Smart Meter Meter Reading Document Creation MDUS then acknowledges the
request by invoking Change based on Smart Meter Meter Reading Document Creation Confirmation enterprise
service operation, either confirming that it will read the meter as scheduled or that it can't read the meter in
question because it doesn't have POD data.

The MDUS then reads the meter on the date the read was requested: either as soon as possible (for a present or
past date, since it is assumed that the MDUS has already stored readings for past dates) or on the specified date
(in the case of a future date). The MDUS sends the meter reading to SAP for Utilities by invoking the Create
Meter Reading Document Result enterprise service operation, which uses the Meter Reading Document business
object. After SAP for Utilities has uploaded the meter reading document, it sends a confirmation message back to
the MDUS, invoking the Confirm Meter Reading Document Result Creation enterprise service operation

The following table summarizes the steps in this use case and the associated enterprise services:

Step Invoked Enterprise Service Operation

Step 1: SAP for Utilities sends a request to Request Smart Meter Meter Reading Document Creation
MDUS to read a certain meter as of a given
date, past or future

Step 2: The MDUS acknowledges the request Change Based on Smart Meter Meter Reading Document
and informs SAP for Utilities of any Creation Confirmation
exceptions (such as the meter ID does not
match its information)

Step 3: The MDUS performs the reading and Create Meter Reading Document Result
sends it to SAP for Utilities

Step 4: SAP for Utilities confirms that it Confirm Meter Reading Document Result Creation
received and uploaded the reading

Use Case 5: Uploading Usage Data to SAP EDM

The services provided in this use case offer an updated set of enterprise services and improved underlying
functionality, that provide runtime-optimized processing of interval usage data.

To create a bill in SAP S/4HANA, information about utilities usage must be uploaded from the meter to SAP ERP
6.0. Live meters can collect usage data at regular intervals, for example every 15 minutes. This data is then
uploaded to the AMI system usually once a day. Since bills are typically created monthly, the profile data is
uploaded to SAP S/4HANA at least once a month. In the past, uploading profile data from the metering system
platform to SAP for Utilities required a labor-intensive customized integration. Using enterprise services has now
significantly improved the process. Furthermore, the uploading process can be monitored allowing navigation to
the corresponding XML messages.

Profile data uploads are triggered on a regular basis to produce a bill. The AMI system sends profile data as bulks
to the SAP NetWeaver Process Integration, which then sends it to SAP backend systems by invoking the
enterprise service Create Utilities Time Series Item As Bulk All the profile data is then uploaded to SAP ERP 6.0,
where it can be used to create the customer's bill. As confirmation that the data was received, SAP ERP 6.0 in
turn triggers the Confirm Utilities Time Series Item Creation As Bulk service operation, which is sent to SAP
NetWeaver PI. PI then formats an XML message that sends a confirmation to the AMI system.

Related enterprise services can be used as required.

The following table summarizes the steps for performing an initial upload of profile data and the associated
enterprise services:

Step Invoked Enterprise Service Operation

Step 1: At the scheduled time, the AMI Create Utilities Time Series Item As Bulk
system sends data to SAP for Utilities

Step 2: SAP for Utilities confirms that the data Confirm Utilities Time Series Item Creation As Bulk
was received

The following table summarizes the steps for performing a follow-up upload of profile data and the associated enterprise
services:

Step Invoked Enterprise Service Operation

Step 1: At the scheduled time, the AMI Change Utilities Time Series Item As Bulk
system sends changed data to SAP for
Utilities

Step 2: SAP for Utilities confirms that the data Confirm Utilities Time Series Item Change As Bulk
was received and changed

Use Case 6a: Remotely Disconnecting and Reconnecting a Meter

This use case explains how a utilities company could use the AMI ES bundle to remotely disconnect a customer
who has not paid their bill. It also explains how the services in this bundle can be used to remotely reconnect a
customer once the bill has been paid.

A utilities company would only use the enterprise services in the Advanced Meter Infrastructure ES bundle to
disconnect a meter following a defined process of attempting to to get the customer to pay the outstanding bill.
The process begins when a utilities company sends a customer a regular monthly bill. If the customer does not
pay the bill in a timely fashion, they are placed on a list of dubious customers. As a result, the following process
steps could be performed: escalating the bill to dunning level 1, which entails sending a mail to the sales manager
and a reminder to the customer. If the customer still refuses to pay the bill, the process moves to dunning level 2,
which requires calling the customer and perhaps taking other measures such as load reduction.

Table 1. Sample Collection Strategy and Related Activities

Dunning Level 1 Activities for Dunning Level 1

Send mail to sales manager

Send reminder to customer

(Other activities defined for this dunning level)

Dunning Level 2 Activities for Dunning Level 2

Disconnection warning call

 Dunning Level 1 Activities for Dunning Level 1

Load reduction

(Other activities defined for this dunning level)

Dunning Level 3 Activities for Dunning Level 3

Load reduction

Start remote disconnection process

If the customer still does not pay, the collection strategy escalates to dunning level 3 and the call center begins
the disconnection process.

A call center employee logs on to SAP for Utilities. The employee then fills out and submits a disconnection
document (see Figure 2) that details the ID of the meter to be disconnected and the date when service will end.
This triggers the enterprise service Request Utilities Connection Status Change Request. The request is sent
from SAP for Utilities to SAP NetWeaver PI. PI then formats an XML message with these details and sends it to
the MDUS system. The MDUS system then transmits a message to the meter to switch itself off, using a
communications technique such as GSM, GPRS, or broadband over power lines. The AMI system then sends an
XML message back to SAP NetWeaver PI, which triggers the Change Utilities Connection Status Change
Request based on Confirmation enterprise service operation, which confirms to SAP for Utilities that the meter
has in fact been disconnected.

Figure 3. Disconnection screen

Reconnection
To reconnect the service, the customer contacts the utilities company and pays the bill. The agent then fills out a
reconnection form in SAP for Utilities (see Figure 3), which also triggers the Request Utilities Connection Status
Change Request enterprise service operation, this time with a parameter that states that the meter should be
reconnected. Power is remotely restored to the customer, and the meter sends back a message that triggers
the Change Utilities Connection Status Change Request based on Confirmation enterprise service operation,
which confirms the processing of the reconnection to the SAP backend system.

The following table summarizes the steps involved in disconnecting or reconnecting a customer and the
associated enterprise services:
 Step Invoked Enterprise Service Operation

Step 1: The customer does not pay his bill No enterprise services is invoked during
this step

Step 2: The customer's delinquent account reaches a dunning No enterprise services is invoked during
level that requires disconnection of the service this step

Step 3: A call center employee fills in a disconnection or Request Utilities Connection Status
reconnection document in SAP for Utilities, which sends a Change Request
message to the MDUS

Step 4: The MDUS confirms that the meter has been Request Smart Meter Utilities Connection
disconnected (or reconnected) Status Change Request Creation or
Change Based on Smart Meter
Connection Status Change Request
Create Confirmation

Figure 4. Reconnection screen

Use Case 6b: Manually Disconnecting and Reconnecting a Smart Meter

In contrast to use case 6a, the smart meter is not disconnected or reconnected remotely. Instead, a service
technician disconnects and reconnects the smart meter manually. The change of disconnection status is sent to
the external MDUS system, so that MDUS can observe the disconnection status in VEE processing. If the
disconnection status is not connected to MDUS, MDUS is not aware of the correct status and is not able to
perform VEE processing.
Use case 6b works similarly to 6a, and involves the following process steps:

Step Invoked Enterprise Service

Operation

Step 1: The customer does not pay their bill No enterprise service is invoked
during this step

Step 2: The customer's delinquent account reaches a dunning level No enterprise service is invoked
that requires the service to be disconnected during this step
 Step Invoked Enterprise Service
Operation

Step 3: A call center employee fills in a disconnection or reconnection No enterprise service is invoked
document in SAP for Utilities, creating a service order that is executed during this step
by a service technician

Step 4: The disconnection / reconnection is executed manually by the Notify of Smart Meter Utilities
service technician, the disconnection / reconnection document is Connection Status Change Request
updated in the system, the information is sent to MDUS as Bulk

Optional step 5: If the disconnection / reconnection is cancelled, the Notify Cancellation of Smart Meter
information is sent to MDUS Utilities Connection Status Change
Request as Bulk

Use Case 7: External Profile Calculation

To create a bill in SAP S/4HANA, information about utilities usage must be uploaded from the meter to SAP ERP
6.0. Usage data is collected every 15 minutes for live meters registered in an AMI system. This data is then
uploaded - usually once a day - to the AMI system. Since bills are typically created monthly, this profile data is
then uploaded to SAP ERP 6.0 at least once a month. This profile data is used to bill customers based on
accurate and flexible time-of-use rates. A time-of-use rate allows you to record different price blocks for each day
(for example on, off, and critical peak times). SAP for Utilities supports two approaches for the time-of-use-based
billing process. One approach uploads all profile data to the SAP for Utilities Energy Data Repository. The billing
process accesses the profile data in the repository and performs actions such as the aggregation of profile values
to retrieve the total consumption within a time-of-use block. The services required for this process are listed in use
case 8: Event Management. The second approach does not upload the profile data to SAP for Utilities. In this
case, the data is stored in the external meter data repository and is accessed using an enterprise service. This
service performs the requested action, such as an aggregation, directly in the external meter data repository and
only returns the results to SAP for Utilities. The subsequent billing process catches the data and prepares a billing
document.

The following table summarizes the steps in this use case and in the associated enterprise services:

Step Invoked Enterprise Service Operation

Step 1: Schedule customer billing No service available

Step 2: Prepare time series calculation request No service available

Step 3: Request time series calculation data Request Utilities Time Series Calculation Creation as Bulk
from external system

Step 4: Receive time series calculation data See service above

from external system

Step 5: Bill customer based on requested data Change Based on Utilities Time Series Calculation
Creation Confirmation as Bulk
Use Case 8: Event Management
Smart meters can communicate with an AMI Head End system and share information about their current status.
They also inform the head end system about events that have occurred (such as an outage or a meter
malfunction). Selected events are forwarded from the head end to SAP for Utilities, where the event data is
analyzed and follow-up actions are created. For example, in the case of a meter malfunction, SAP for Utilities can
create a workforce order to repair the meter.

The following table summarizes the steps in this use case and in the associated enterprise services:

Step Invoked Enterprise Service

Operation

Step 1: External system sends AMI event message to SAP for Utilities Create Utilities Smart Meter Event
as Bulk

Step 2: SAP for Utilities analyzes the event message and prepares a No service available
follow-up action

Use Case 9: Text Messaging to AMI Device

Modern smart meter devices can receive and display text messages sent by SAP for Utilities. This feature
provides the utilities company with new means of communicating with customers. For example, the utilities
company can inform the customer about the progress of inquiries or send out a dunning notice.

The following table summarizes the steps in this use case and in the associated enterprise services:

Step Invoked Enterprise Service Operation

Step 1: Compose message in SAP for Utilities No service available

Step 2: SAP for Utilities sends out a text message to an AMI Notify of Utilities Device Smart Meter Text as
device Bulk

Utilities Business Object Definitions

Utilities Device

Measurement Processing

Meter Reading Document

Utilities Data Type Catalog

https://help.sap.com/http.svc/rc/cb28123a952a4eb5897f5ed52c04de1d/1.0.0/en-
US/UTILITIES_DT_Catalog_1_2.pdf
Utilities Device Management Service Operations Documentation (Use Cases 1, 2)

Notify of Utilities Device Smart Meter Location

Notify of Utilities Device Smart Meter Registration

Notify of Utilities Device Smart Meter Relationship

Notify of Utilities Device Smart Meter Text as Bulk

Query and Change for Utilities Device Smart Meter Operational State by ID

Request and Confirmation for Utilities Device Smart Meter Bulk Cancellation

Request and Confirmation for Utilities Device Smart Meter Bulk Replication

Request and Confirmation for Utilities Device Smart Meter Change

Request and Confirmation for Utilities Device Smart Meter Creation

Request and Confirmation for Utilities Device Smart Meter Register Change

Request and Confirmation for Utilities Device Smart Meter Register Creation

Utilities Meter Reading Service Operations Documentation (Use Cases 3a, 3b, 4)

Change Meter Reading Document Result

Create Meter Reading Document Result

Notify Meter Reading Document Result as Bulk

Notify Utilities Measurement Task Device Assignment Out

Notify Utilities Measurement Task Out

Request and Confirmation for Smart Meter Meter Reading Document Cancellation

Request and Confirmation for Smart Meter Meter Reading Document Creation

Request and Confirmation for Smart Meter Meter Reading Document Result Change

Request and Confirmation for Smart Meter Meter Reading Document Result Creation

Request and Confirmation for Smart Meter Utilities Measurement Task Change

Utilities Time Series Service Operations Documentation (Use Cases 5, 7)

Read Utilities Time Series Item

Request and Confirmation for Create Utilities Time Series Item as Bulk

Request and Confirmation for the Change of Utilities Time Series Items as Bulk

Request and Confirmation for the Change of Utilities Time Series Meas. Task Assignm
Request and Confirmation for the Creation of Utilities Time Series Calculation as Bulk

Request and Confirmation for the Creation of Utilities Time Series Items as Bulk

Request and Confirmation for Utilities Time Series Calculation Cancellation as Bulk

Request and Confirmation for Utilities Time Series Replication as Bulk

Utilities Connection Processing Service Operations Documentation (Use Cases 6a, 6b)

Notify Canc of Smart Meter Util Connect Status Change Req as Bulk

Notify Smart Meter Util Connection Status Change Request as Bulk

Req and Conf for Smart Meter Util Connection Status Cancellation

Req and Conf for Smart Meter Util Connection Status Creation

Utilities Event Management Service Operations Documentation (Use Case 8)

Req and Conf Utilities Smart Meter Event Creation as Bulk

Utilities Point of Delivery Management Service Operations Documentation (Use Cases

1, 9)
Notify of Smart Meter Utilities Point Of Delivery External ID