SAP Help - IsU Device Management

Device Management

PDF download from SAP Help Portal:

http://help.sap.com/erp2005_ehp_07/helpdata/en/57/91d0533f8e4308e10000000a174cb4/frameset.htm Created on December 19, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

1 Device Management

1.1 Technical Device and Connection Data

1.1.1 Register Group

1.1.1.1 Sample Register Relationship

1.1.2 Input/Output Group

1.1.3 Command Group

1.1.3.1 Creating Command Groups

1.1.4 Winding Group

1.1.5 Device Category

1.1.5.1 Device Category Creation

1.1.5.2 Creating Device Categories in IS-U

1.1.6 Equipment

1.1.6.1 Device Creation

1.1.6.1.1 Inspection Relevance

1.1.6.2 Creating Devices in Plant Maintenance

1.1.6.3 Creating Devices in Inventory Management

1.2 Device Installation

1.2.1 Device Information Record

1.2.2 Device Grouping

1.2.3 Installing, Removing or Replacing Devices

1.2.4 Device Installation

1.2.4.1 Device Installation

1.2.5 Device Removal

1.2.5.1 Device Removal

1.2.6 Device Replacement

1.2.6.1 Device Replacement

1.2.6.2 Replacement of Device Group with Another Device Gr

1.2.6.3 Replacement of Device Group with Smaller Device Gr

1.2.6.4 Replacement of Device Group with Larger Device Gro

1.2.6.5 Repl. of Dev. Group with Dev. Grp with Special Tec

1.2.6.6 Replacement of Devices in a Device Group

1.2.6.7 Replacement of Device Group with Complex Device

1.2.6.8 Replacement of Complex Device with Device Group

1.2.7 Reversal of Technical Installations, Removals and Replacements

1.2.7.1 Reversing Device Installations

1.2.7.2 Reversing Device Removals

1.2.7.3 Reversing Device Replacements

1.2.8 Device Modification

1.2.8.1 Device Modification

1.2.8.1.1 Entry of Meter Reading Results During Modification

1.2.8.1.2 Allocation of Different Device Category via MM-IM

1.2.8.1.3 Allocation of Different Device Category via PM

1.2.9 Installation Structure

1.2.9.1 Device Allocation

1.2.9.1.1 Creating Device Allocations

1.2.9.2 Rate data

1.2.9.3 Register Relationship

1.2.9.4 Period consumption

1.2.9.4.1 Period Consumption and Usage Factor Concepts

1.2.9.5 Logical Register Number

1.2.9.5.1 Changing Logical Register Numbers

1.3 Reading Meters

1.3.1 Base Period

1.3.2 Weighting Procedure

1.3.2.1 Examples for Mixed Weighting

1.3.3 Extrapolation

1.3.3.1 Extrapolation for Consumption Registers

1.3.3.2 Extrapolation for Demand Registers

1.3.3.3 Extrapolation for Resetting Registers

1.3.3.4 Extrapolation with Billing Factor

1.3.3.5 Proration of Meter Readings

1.3.3.6 Extrapolation of Demand from Billing

1.3.4 Meter Reading Organization

1.3.4.1 Street Route

1.3.4.1.1 Maintain Street Route for Meter Reading Unit

1.3.4.2 Planning Meter Readers

1.3.4.3 Mass Changes to Meter Reading Units

1.3.5 Meter Reading Order

1.3.5.1 Meter Reading Order Creation

1.3.5.1.1 Single Order Creation

1.3.5.1.2 Mass Order Creation

1.3.5.1.3 Meter Reading Control

1.3.5.1.4 Reversal

1.3.5.2 Order Output

1.3.6 Meter Reading Result

1.3.6.1 Entry of Meter Reading Results

1.3.6.1.1 Upload

1.3.6.1.2 Fast Entry With/Without Correction

1.3.6.1.3 Single Entry

1.3.6.1.4 Assessing

1.3.6.2 Correction of Meter Reading Results

1.3.6.2.1 Upload

1.3.6.2.2 Correction of Plausible Meter Reading Results

1.3.6.2.3 Correction of Implausible Meter Reading Results

1.3.6.3 Validations

1.3.6.3.1 Independent Validation

1.3.6.3.2 Dependent validations

1.3.6.4 Estimation

1.3.7 Reversal

1.3.8 Monitoring

1.3.8.1 Monitoring of Meter Reading Results

1.3.8.2 Device Overview

1.3.9 Quantity Determination

1.3.9.1 Quantity Determination During Meter Reading

1.3.9.1.1 Important Notes

1.3.9.1.2 Notes About the Time of the Changeover

1.3.9.1.3 Concepts

1.3.9.1.3.1 Change Meter Reading Results

1.3.9.1.3.2 Quantity Determination Trigger Concept

1.3.9.1.3.3 Check for Final Determined Consumption in Technical Transactions

1.3.9.1.3.4 Estimation Procedure

1.3.9.1.3.4.1 Extrapolation

1.3.9.1.3.4.2 Interpolation

1.3.9.1.3.4.3 Interaction - Estimation and Actual Meter Reading

1.3.9.2 One-Off Activities for Changeover

1.3.9.2.1 Check Company-Specific Starting Point

1.3.9.2.2 Defining the Quantity Determination Procedure

1.3.9.2.3 Defining the QD Procedure for Existing Installations

1.3.9.3 Activities in Production Operation

1.3.9.3.1 Process Quantity Determination Trigger

1.4 Device Inspection

1.4.1 Device Inspection

1.4.2 Sampling Procedure

1.4.2.1 Sampling Procedure

1.4.2.1.1 Official/Internal Lots

1.4.2.1.2 Lot Compilation

1.4.2.1.2.1 Compiling Lots

1.4.2.1.2.2 Deleting Devices or Device Categories from Lots

1.4.2.1.3 Determination of Lot Devices

1.4.2.1.4 Drawing of Sample Devices

1.4.2.1.4.1 Drawing Sample Devices

1.4.2.2 Sampling Procedure for Canada

1.4.3 Periodic Replacement

1.4.3.1 Creation of Periodic Replacement Lists

1.4.3.2 Work Order or Notification Creation

1.4.3.3 Work Order Printout

1.4.4 Certification

1.4.4.1 Certification

1.4.4.2 Seal Extension

1.4.5 Recording Device Inspection Data in Quality Management

1.5 Country Specific Functions

1 Device Management

Purpose

This component manages technical data, installations, meter readings, and the inspection of devices.

If you have activated the Advanced Metering Infrastructure business function (ISU_AMI_1) and you are in an advanced metering infrastructure, you can find more information under Advanced Metering Infrastructure .

Integration

The following table lists the standard application components that must be integrated into device management before you can manage devices.The device, device category, and device number in the Utilities Industry (IS-U) component correspond to equipment, material, and the serial number in the standard system: Names in IS-U and the Standard System

Name in IS-U From component Name in Standard System

Device Plant Maintenance (PM) Equipment

Device Category Logistics Basic Data (LO-MD) Material

Device Number Logistics Basic Data (LO-MD) Serial Number

The device number is created in MM with the Goods Receipt function and transferred to the device. The device number can also be generated when you create a device in IS-U. The device is identified by a unique material and serial number combination to distinguish it from other pieces of material that may have the same serial number. The equipment number is the same throughout the system.

Integration of IS-U with MM, LO and PM

MM is also used for the following functions in device flow: MM Functions for Device Flow

Function Component

Procurement Purchase Requisition and Purchase Order from (MM-PUR)

Delivery Goods Receipt from Inventory Management (MM-IM)

Outward Movement (such as scrapping or sales) Goods Issue and Return Delivery from MM-IM

Stock Transfer Goods Issue and Return Delivery from MM-IM

Equipment records are created automatically at goods receipt .Therefore, functions of the PM application component are used, including standard ordering functions and creation of maintenance plans or task lists. Billing is then carried out with the Sales and Distribution (SD) component.

For more information, see: PM: Equipment

LO-MD:

Serial Number Management MM-PUR:

MM-IM:

Goods Receipts for Purchase Orders

Purpose

This component manages technical and connection data of devices:

Note

A connection may be the input and output of a transformer, for example. This type of connection should not be confused with the connection of a connection object to the supply line.

1.1.1 Register Group

Purpose

This component groups together the registers of one device category or one device, including technical data (such as number of digits and type of display) and billing data (such as rate usage type). Registers meter consumption and demand. Registers can be actual physical devices or displays in electronic devices.

Features

You can manage registers of different division categories in one register group. You can allocate a main division category to the register group. At least one register of the register group must be in the main division category.

1.1.1.1 Sample Register Relationship

Use

This function allows you to allocate a sample register relationship to a register group.

Features

You have the following options when using this function:

You can create several sample register relationships for each register group. You can use any sample register relationships possible within a register group.

When you install devices you can adopt the sample register relationships of the register group and create them as functional register relationships. If you change an existing sample register relationship, there is no effect on installed devices.

Processing and checks are the same as those for normal Register Relationships .

1.1.2 Input/Output Group

Purpose

This component groups together the inputs and outputs of a device category or device and provides technical data of these devices. Inputs and outputs are interfaces for devices. Remote meters have several pulse inputs and a modem interface.

1.1.3 Command Group

Purpose

This component allows you to define commands and group them together. A command is a signal sent by the utility company that triggers a switching procedure in a ripple control receiver.

Example

For example, the command group for street lights might consist of the commands switch-on , decrease demand , and switch-off .

1.1.3.1 Creating Command Groups

Prerequisites

You have created the appropriate commands for the command group. Procedure

To create a command group choose Utilities industry Command/comm. group Create command group

1.1.4 Winding Group

1.1.4 Winding Group

Purpose

This component groups together windings of one device or device category. Windings define the transformation ratio (of transformers, for example) and are divided into primary and secondary windings. A winding group contains at least one primary and one secondary winding.

You can define a text field for the winding demand in Customizing under Define Winding Demand.

You can deactivate checks for maximum current and voltage in Customizing. To do this, go to Technology Winding Group Define System Parameters for Winding Groups .

Implementation considerations

This component is optional. It is only required if you use transformers.

1.1.5 Device Category

Purpose

This component manages device categories. Each device belongs to a certain device category. The device category groups together all devices with similar features (for example, price class, register group, or certification data).

The various device categories can then be allocated to the following basic device categories : Counter

Transformer Power transformer

Audiofrequency ripple control receiver Remote meter Counter Corrector Pressure regulator Sensor Other

One device category can also be a combination of different device categories.

Integration

The device category corresponds to the material in the Logistics Basic Data (LO-MD) application component. For more information, see LO-MD:

Material Master

Serial Number Management

1.1.5.1 Device Category Creation

Use

This function allows you to create device categories in the Utilities Industry (IS-U) component. Integration

This function is integrated with the application components Logistics (L0) and Materials Management (MM).

The IS-U device category is an extension of the Material master in the Basic Logistics Data (LO-MD) application component. You maintain the material master in the Materials Management (MM) application component.

Features

You have the following options for creating a device category: You can create the material master in MM first .

When you do this, a material master for IS-U is automatically created in the background.

Subsequently, you must extend this material master in IS-U as a device category with IS-U-specific data. You can only create the material master as a device category in IS-U.

When you do this, a smaller version of the material master is created automatically in the background for MM. However, this material master does not allow you to use all of the functions of MM.

If you want to use all of the MM functions available, you must extend the material master you created in IS-U later in MM.

Note

If you use MM, we recommend the first option above. Prerequisites

Register groups Input/output groups Command groups

Inspection point groups (optional)

Winding groups (only required for transformers)

1.1.5.2 Creating Device Categories in IS-U

Procedure

1. Choose Utilities industry Device management Technology Device category Create. You branch to the initial screen for creating device categories.

2. Enter the required data and choose a basic device category to be allocated to the device category. Chose Continue .

If a material exists for the device category specified, you branch to the screen Create Device Category: General Data. Go to step 3. If no material exists for the device category specified, the Create MM Material dialog box appears.

Here you can create a material in MM in the background. Processing is then continued on the next screen for device category maintenance. 3. Enter further data for the device category and if necessary add additional basic device categories. Save your data.

You branch to the initial screen for creating device categories. Result

The device category was created in IS-U. In addition, a material master was created in the background.

If you want to use all of the MM functions available, you must extend the material master you created in IS-U in MM.

1.1.6 Equipment

Purpose

This component manages the equipment of a utility company.

Integration

The equipment is uniquely identified in the system by the following: The equipment number in PM

The combination of serial number and material number in the Logistics Basic Data (LO-MD) component For more information, see:

The Technical Objects component (PM-EQM): Equipment

The Logistics Basic Data component (LO-MD):

Material Master

Serial Number Management The Purchasing component (MM-PUR):

Purchase Requisitions Purchase Orders

The Inventory Management component (MM-IM):

Planning Goods Receipts

Goods Receipts for Purchase Orders

Goods Receipts for Orders Other Goods Receipts Goods Issues

Transfer Postings and Stock Transfers

1.1.6.1 Device Creation

Use

This function allows you to create devices in the Utilities Industry (IS-U) component. For each device, a master record with IS-U-specific data is created in addition to a corresponding piece of equipment in the Plant Maintenance (PM) application component.

Integration

This function uses many functions from the Plant Maintenance (PM) application component.

Prerequisites

You have created the appropriate device category for the device.

Features

In IS-U via the Technical Device and Connection Data (IS-U-DM-TD) component. You do this by using the Create material serial number function in PM that was enhanced for IS-U.

The device is only created as a piece of equipment, but the material stock in the Inventory Management (MM-IM) application component is not updated. You can create several devices simultaneously via list editing.

In MM-IM via goods receipt

You can create any number of devices with different device categories. The material stock is updated accordingly.

You can assign any default entries to the fields in the Create IS-U data dialog box, which appears when you create a device. To do this, use function module EXIT-SAPLE10R_002 in enhancement EDME10L1.

You can now use function module EXIT_SAPLIPW1_008 from enhancement IQSM0008 when you create a material serial number and equipment. This means that every time you create a device, the corresponding combination of material and serial number undergoes further user-defined checks.

1.1.6.1.1 Inspection Relevance

Use

You use this function to determine whether a particular device, such as an external device, is to be included in a Sampling Procedure.

Prerequisites

You have established settings for inspection relevance in Customizing. To do this, go to Utilities Industry Device Management Inspection Sampling Procedure Define Inspection Relevance of Devices .

1.1.6.2 Creating Devices in Plant Maintenance

Prerequisites

The appropriate device category for the device has been created. Procedure

Note

To create several devices at once in the Plant Maintenance application component, choose Utilities Device management Technology Device List editing Create .

1. Choose Utilities industry Device management Technology Device Create. 2. You branch to the initial screen for creating material serial numbers.

3. Enter the material number, and if necessary the serial number and the equipment category used for IS-U devices. Chose Continue . 4. The Enter IS-U data dialog box appears.

5. Enter the required data. Choose Transfer .

6. You branch to the screen Create material serial number: IS-U data. 7. Enter the required data.

8. Save your data. Result

The device has been created as a piece of equipment in the Plant Maintenance application component.

Note

The material stock of the Inventory Management (MM-IM) application component was not updated.

1.1.6.3 Creating Devices in Inventory Management

Prerequisites

The appropriate device category for the device has been created.

Procedure

1. Choose one of the following menu paths:

Utilities Industry Device Management Technology Device Inventory Management Logistics Materials Management Inventory Management

The Enter Goods Receipt: Initial Screen appears.

Note

The type of goods receipt you choose is dependent on your previous processing steps. For example, if you have created an order for the devices to be created, choose Goods Receipt For Order . In the most straightforward example, choose Goods Receipt Other .

1. Enter the required data. Choose Continue . The Enter Goods Receipt: New Items screen appears.

1. Enter the material, quantity and any other data required. Choose Continue . The Maintain Serial Numbers dialog box appears.

1. Choose Create Serial Number Automatically or enter the number manually. Choose Previous Screen . 2. The Enter IS-U Data dialog box appears.

3. Enter the required data. Choose Copy .

The Enter Goods Receipt: Collective Processing screen appears. ( )

From the Enter IS-U Data screen, you can access the classification system in which you can classify devices using your own criteria. Choose Classification . 1. Save your entries.

You can now enter additional devices as described above.

Result

The device has been created as a piece of equipment in the Plant Maintenance and Service Management (PM) component. The material stock in the Inventory Management component (MM-IM) was updated.

1.2.4.1 Device Installation

Purpose

This component allows you to do the following: Install, remove, and replace devices

You establish or terminate a link between a device and a device location (technical view) and an installation (billing view).

You can override certain system parameters defined by SAP for installation, removal or replacement. Establish settings as required in Customizing. To do this, choose Device Management Installation Basic Settings Define System Parameters for Installation/Removal/Replacement .

Create device groups

Change rate data and technical data of devices that are already installed in a utility installation.

Integration

You can use the IDoc ISU_DEVICE_CHANGE to transfer data from external systems to the work process.You can enter one meter reading result per action.It is currently not possible to process multiple meter readings.

If a meter reading is implausible, IDoc processing is not canceled.You can correct the reading.For more information, see Correction of Implausible Meter Reading Results .

To transfer meter reading results to workflow for further processing, use the role ISU_MREADER for the agent. Further information on IDocs:

For general information, see IDoc Interface/Electronic Data Interchange For detailed information, see Using Documentation Tools

Here you determine which documentation you can display for a certain IDoc.

You can integrate functions for transferring devices prior to installation or after removal into device installation, removal and replacement. You have the following options:

Installation and removal

You can enter the target plant and storage location as well as the movement type on the initial screen. Device replacement

You can enter goods movement data (target plant and storage location and movement type) for device removal and installation. You can also enter other data such as the cost center.

To activate these functions, you have to define parameter GOODSMVMT in Customizing under Installation System Parameters for Installation/Removal/Replacement .

Device installation, removal, and replacement now contains the following enhancements: EDMD1001 (user-defined default values for installation, removal and replacement) This enhancement allows you to define default data for input parameters. EDMD1001 (user-defined checks for installation, removal and replacement) This enhancement allows you to implement your own input checks.

Meter Data Unification and Synchronization (MDUS) System Notification for AMI devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you:

Install an AMI device (for example, a smart meter or advanced meter)in a new device location. Make installation modifications to an AMI device

Remove an AMI device from a device location

1.2.1 Device Information Record

Definition

The device information record is an object in the IS-U system that enables the system to perform billing-orientated functions.

Use

When carrying out billing functions, the complete IS-U Device Management (IS-U-DM) does not have to be used. Instead, you can create a device information record that only manages device data required for billing, for example, rate data, device allocations, register relationships and maintenance of logical registers.

About AMI-relevant device information records

If you are working within an advanced metering infrastructure, you can indicate that device information records are AMI-relevant. In this case the devices and device information records have additional attributes: For more information, see Advanced Metering Infrastructure .

Remote disconnection and reconnection processes also apply to device information records.However, you can prevent remote disconnection or reconnection by implementing a validation within the BAdI ISU_AMI_DISCONNECT .

Integration

There is no longer a connection to Plant Maintenance (PM) . Communication with other systems, such as importing consumption data, takes place via the point of delivery.

1.2.2 Device Grouping

Purpose

In this component you can group together devices that form a logical unit. All devices in a device group must currently either be installed or not installed. If you install or remove a device in a device group , all other devices in the group are automatically drawn for removal or installation. This ensures that devices that belong together are not accidentally installed or removed. You must confirm the replacement of each device in a device group.

Implementation considerations

This component is optional. You should create a device group if, for example,

Current and voltage transformers are placed into transformer groups, resulting in a certain transformation ratio. Two water meters are installed together as one integrated water meter.

Features

Maintain and display the history of the device group

When you do this, you can change the current time slice. You can decide whether the device group is to be prorated to the change date, that is, whether you wish to start a new time slice. You can display change documents and creation data.

Inspect the device group

The system checks the device group for general and special restrictions. For more information, see the online help for the following fields: Device group

Group type Group category

Terminate the device group.

When you terminate a device group, all devices are removed from the group. The device group is empty and can be used for new devices. Delete the device group.

When you delete a device group, it is deleted from the system entirely.

1.2.3 Installing, Removing or Replacing Devices

Installing, removing or replacing a single device

1. Enter your device (enter both devices in the case of a replacement).

2. Enter the required data on the screen for either installation, removal, or replacement. 3. Save your data.

Installing, removing or replacing a device from a device group

Enter a device from the group on the initial screen. If you are replacing a device, enter a device from each group. a) Choose Enter .

The rest of devices of the group are display in the worklist. b) Choose Enter.

Process the work list.

Enter the required data for each device on the screen for either installation, removal, or replacement. Save your data.

Installing, removing or replacing several devices

1. Do not enter a device, device category or division.

2. Enter the devices in the worklist or set the Rem. (removal) indicator. 3. Process the work list.

4. Enter the required data for each device on the screen for either installation, removal, or replacement. 5. Save your data.

Meter Data Unification and Synchronization (MDUS) System Notification for AMI devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you install, remove or replace an AMI device (for example, a smart meter or advanced meter) in a new device location.

1.2.4.1 Device Installation

Purpose

In this component you can enter an initial or additional installation of a device in different ways.

In the case of a technical installation , a device is linked to a device location. In the case of a billing-related installation , the device is linked to a utility installation. A device must first be installed in a device location before it can be allocated to several installations.

Full installation enables you to link a device to both a device location and a service installation in one step.

You can reverse a technical installation. For more information, see Reversal of Technical Installations, Removals and Replacements

Features

Installation includes the following functions: Allocation of devices (e.g. transformer to meter) Entry of periodic consumption

Entry of meter readings recorded at the time of installation Creation of register relationships

Adopting Sample Register Relationships

Note

You can define a default measured pressure for technical installation. To do this, you have to establish settings in Customizing under Device Management Installation Basic Settings Define System Parameters for Installation/Removal/Replacement and Contract Billing Special Functions Gas Billing Volume Correction Factor Measured Pressures Define Measured Pressures.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, t he system notifies the MDUS as soon as you install an AMI device (for example, a smart meter or advanced meter) in a new device location.

1.2.4.1 Device Installation

Purpose

You can install devices in the following ways:

Technicalinstallation only, for example if a meter is not to be billed. This would apply in the case of a control meter or a meter that belongs to the utility company. First technical, then billing-related installation, for example if

Meters in an apartment building are installed first and assigned to apartments later

Both steps are carried out by different agents

One technical installation and several billing-related installations. This would apply in the case of a pressure regulator or an ARCR that controls several installations.

Fullinstallation, as in the case of a single-family home.

Prerequisites

When you enter the device installation, the device must not have been modified or changed in the system after the actual installation date. The entry in the system must correspond to the actual history of the processes.

You enter the installation on 10/12. The installation took place on 10/08. A device modification or a change to the device data may not have been entered after 10/08.

You must perform a technical installation before you can perform a billing-related installation.

In the case of technical installations, the same prerequisites apply as for the installation of a piece of equipment ( Device ) in a functional location ( Device location ) in the Plant Maintenance application component.

For more information see the following in the Technical Objects (PM-EQM) application component:

Functional locations Equipment

Equipment at Functional Locations

Process flow

Device installation includes the following phases:

An installation order for a device or a device group is created in the Service Management (PM-SMA) application component. This may result from a company requirement (such as a switching change) or an external requirement (new connection),

The installation order is executed and returned. The removal of the device is entered in IS-U.

Here the device always undergoes a technical installation and if it is to be billed, it undergoes a billing-related installation. For more information, see Installing, Removing, and Replacing Devices

Note the following:

If the device belongs to a device group, the entire device group must be installed in the case of technical installations and full installations. In the case of technical and full installations you have to change the register group configuration.

Those registers are proposed for which the PR (Propose register during installation/replacement) field has been selected.

You can change the register configuration in Customizing under Change Register Configuration . You can the select any register in the register group.

Result

The device is installed in the device location. This corresponds to the installation of a piece of equipment in a functional location. This enables you to use all PM functions for installed equipment.

The system stores technical data for the register.

Device relationships may have been created and a device location is created. Billing-related installation

The device is allocated to an installation for billing.

The system creates billing-related data for the device and registers of the installation. The device can be billed.

Full installation

The device is installed in the device location with respect to technical data The device is allocated to an installation for billing.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you install an AMI device (for example, a smart meter or advanced meter) in a new device location.

Purpose

You use this component to enter removal of devices. As in the Installation (IS-U-DM-DI-IN) component, removal is divided into technical removal, billing-related removal, and full removal.

All rate data and relationships with other devices are prorated to the removal date (meaning the time slice ends). However, the data can still be traced. Reference values are not prorated automatically. They can be manually prorated or deleted, however.

You can reverse a technical removal. For more information, see Reversal of Technical Installations, Removals and Replacements

Features

For more information, see Device Removal

Device Removal for One Day in Future

For interval meters, you can carry out a technical or billing related device removal for one day in the future.

In Customizing for SAP Utilities under Device Management → Installation → Basic Settings → Define System Parameters for Installation/Removal/Replacement , select parameter REMOVEF1D – Remove, Install for Billing Intrvl Meter for 1 Day in Future . You can also reverse the device removal for one day in the future.

Lot Membership and Certification

A device may lose lot membership or certification regardless of the activity reason. For more information, go to Customizing and choose Device Management → Installation → Basic Settings → Define System Parameters for Installation/Removal/Replacement .

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you remove an AMI device (for example, a smart meter or advanced meter) from a new device location.

1.2.5.1 Device Removal

Purpose

You can install devices in the following ways:

Technicalremoval only, if a device (such as a control meter) has undergone technical installation only. Billing-relatedremoval only, if a device in an installation is no longer to be included in billing

First billing-related and technical removallater, for example if billing and technical areas in a utility company are managed by different employees. One billing-relatedand several billing-related removals. This would apply in the case of a pressure regulator or an ARCR that controls several installations. Fullremoval, for example in the case of a single-family home that is dismantled.

Prerequisites

When you enter the removal, the device must not have been modified or changed in the system after the actual removal date. The entry in the system must correspond to the actual history of the processes.

You enter the removal on 10/12. The actual removal took place on 10/08. A device modification or a change to the device data may not have been entered after 10/08.

Before a technical installation can be performed,

The device must not have already undergone billing-related installation on the removal date The device must not control any other device

No register of the device may be part of a register relationship that is automatically terminated

In the case of technical removals, the same prerequisites apply as for the removal of a piece of equipment ( Device ) from a functional location ( Device location ) in the Plant Maintenance (PM) application component.

For more information see the following in the Technical Objects (PM-EQM) application component:

Functional Locations Equipment

Equipment at Functional Locations

Process flow

Device removal includes the following phases:

A removal order is created for a device or a device group in the Service Management (PM-SMA) application component. This results from a company requirement (such as the dismantling of an object) or an external requirement (new connection).

The removal order is executed and confirmed. The removal of the device is entered in IS-U.

For more information, see Installing, Removing, and Replacing Devices

If the device belongs to a device group, the entire device group must be removed in the case of technical and full removals.

If the last meter is removed from a device in an installation with a valid contract, the system issues either a warning or an error, depending on how you define system parameters for installation/removal/replacement.

Result

The device is removed from the device location. This corresponds to the removal of a piece of equipment from a functional location. The system prorates the technical data of the registers.

Billing-related removal

The system terminates billing-related allocation of the device to the installation. The system prorates the billing-related device and register data of the installation Full removal

The device is removed from device location with respect to technical data The system terminates all billing-related allocations of devices to installations. Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you remove an AMI device (for example, a smart meter or advanced meter) from a new device location.

1.2.6.1 Device Replacement

Purpose

This component allows you to enter the replacement of a device by another device with the same function from the same or similar device category. A device is replaced instead of being both removed and installed if the following data is to be transferred to the new device:

Rate data Register relationships Device relationships

Register-related periodic consumption Disconnected status

You can reverse a technical installation. For more information, see Reversal of Technical Installations, Removals and Replacements

Implementation Considerations

This component is optional because you can also replace a device with the Installation and Removal (ISU-DM-DI-IN or OU) components. However, if you use these components, all links and register relationship are deleted. Therefore, it is often much easier to replace a device. For example, a replacement is necessary if an installed device is damaged or if it is to be certified with the Device Inspection (ISU-DMIS) component.

Integration

You can transfer data to external systems using IDoc ISU_RPL_ORDER. Further information on IDocs:

For general information, see IDoc Interface/Electronic Data Interchange For detailed information, see Using Documentation Tools

Here you determine which documentation you can display for a certain IDoc.

Features

In the case of a replacement, you can enter meter readings recorded at the time of installation or removal.

A device may lose lot membership or certification regardless of the activity reason.For more information, go to Customizing and choose Device Management Installation Basic Settings Define System Parameters for Installation/Removal/Replacement .

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you replace an AMI device (for example, a smart meter or advanced meter).

1.2.6.1 Device Replacement

Purpose

This process enables you to replace devices.

Example

You replace a double-rate meter as part of a periodic replacement or due to damage.

Note

You can replace devices that have different measuring types. However, you may have to change the measuring types in the device allocation data.

Prerequisites

When you enter the replacement, the device must not have been modified or changed in the system after the actual replacement date. The entry in the system must correspond to the actual history of the processes.

Example

You enter the installation on 10/12. The installation took place on 10/08. A device modification or a change to the device data may not have been entered after 10/08.

The same prerequisites apply to the device to be removed as to the removal of a piece of equipment ( Device ) from a functional location ( Device location ) in the Plant Maintenance (PM) application component.

The same prerequisites apply to the device to be installed as to the installation of a piece of equipment (device) in a functional location (device location) in the Plant Maintenance application component.

For more information see the following in the Technical Objects (PM-EQM) application component:

Functional Locations Equipment

Equipment at Functional Locations

Process flow

Device replacement includes the following phases:

1. A replacement order is created for a device or a device group in the Service Management (PM-SMA) application component. This may result from a company requirement (such as a switching change) or an external requirement (such as a change in use of the object).

2. The replacement order is executed and confirmed.

3. The replacement of the device or of all devices in a device group is entered in IS-U. For more information, see Installing, Removing, and Replacing Devices

Note

There are different replacement scenarios for device groups, such as Replacement of a device group with another device group .

Note that replacement orders can only be created for single devices. This means that if the device belongs to a device group, the other devices are not transferred to the order automatically as additional items.

Note

The system automatically checks and prorates the attributes (such as measured pressure, billing factor, or command) of existing device allocations. A message is displayed if the system cannot check attributes automatically.You can go directly to the device allocation and check attributes manually. To do this, choose Goto Device allocations .

Result

The new device adopts all relationships of the old device. If device categories of the devices do not match, it is possible that individual relationships were prorated.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you replace an AMI device (for example, a smart meter or advanced meter).

1.2.6.2 Replacement of Device Group with Another Device Group

Purpose

This process can be used for replacing one transformer group with another transformer group, for example. Process flow

Device group A is replaced with device group B. In this case, the devices to be installed adopt the tasks of the devices to be removed. Replacement of a device group with another device group

( )

1.2.6.3 Replacement of Device Group with Smaller Device Group

Purpose

You can use this process to replace three devices in a meter board with two devices, for example. Process flow

Device group A is replaced with device group B, which contains few devices. The devices to be installed, 1b and 2b, take on the same tasks as the 1a and 2a, the devices to be removed. Device 3a is only removed.

Replacement of device group with smaller device group ( )

1.2.6.4 Replacement of Device Group with Larger Device Group

Purpose

You can use this process to replace two devices in a meter board with three devices, for example. Process flow

Device group A is replaced with device group B, which contains fewer devices. The devices to be installed, 1b and 2b, take on the same tasks as the 1a and 2a, the devices to be removed. Device 3b is only installed with respect to technical data.

Replacement of device group with larger device group ( )

1.2.6.5 Repl. of Dev. Group with Dev. Grp with Special Tech.

Inst.

Purpose

You can use this process to install devices with different tasks in a meter board, for example. Process flow

Device group A is replaced with device group B. The devices to be installed, 1b and 3b, take on the same tasks as the 1a and 3a, the devices to be removed. Device 2a is only removed because the device to be installed, 2b, has another task.

Example

Devices 1a and 1b are active current meters, devices 3a and 3b are watt meters. The device to be removed (2a) is an ARCR, but the device to be installed (2b) is a demand meter.

Replacement of device group with device group with special technical installation ( )

1.2.6.6 Replacement of Devices in a Device Group

Purpose

This process can be used for replacing an audiofrequency ripple control receiver in a meter board, for example. Process flow

A device is replaced within device group A. The device to be installed (4a) has the same task as the device to be removed (1a). Device 4a is now part of the device group. Devices 2a and 3a are not affected.

Replacement of devices within a device group ( )

1.2.6.7 Replacement of Device Group with Complex Device

Purpose

This process can be used for replacing a meter board with a complex meter, for example. Process flow

Replacement of device group with complex device ( )

1.2.6.8 Replacement of Complex Device with Device Group

Purpose

This process can be used for replacing a complex meter with a meter board, for example. Process flow

Complex device 4 is replaced with device group A. The tasks of the complex device are transferred to the individual devices of the device group. Replacement of complex device with device group

( )

1.2.7 Reversal of Technical Installations, Removals and

Replacements

Use

You use this function to reverse a technical installation, removal or replacement.

If you carried out both a billing-related and a technical installation, removal or replacement, see also:

Reversing Device Removals Reversing Device Installations Reversing Device Replacements

Prerequisites

The device must not have been installed for billing, that is, it must not be allocated to an installation.

Features

Full installation, removal or replacement

This function does not make changes to the data of the following objects: Register relationships and reference values

Statistics records

Device allocations for controlling devices Blocked devices

Device groups

The reversal does not take into account any device transfers you have carried out.

Reverse Installation

When you perform an installation reversal , the following is changed:

Technical installation in the Utilities Industry (IS-U) and Plant Maintenance and Service Management (PM) components are canceled. A removal is carried out in PM at the time of installation.

The allocations of controlled devices (such as those controlled by ripple control receivers) are terminated. The device location that you created during installation is not deleted.

Reverse Removal

A removal reversal results in the termination of a technical removal in the Utilities Industry (IS-U) and Plant Maintenance (PM) components. An installation is carried out in PM at the time of removal.

Reverse Replacement

A reversal replacement results in the termination of a device replacement in the Utilities Industry (IS-U) application component In the Plant Maintenance and Service Management (PM) component, the old device is automatically re-installed and the current device is removed.

Meter Data Unification and Synchronization (MDUS) System Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you reverse an installation, replacement or removal of an AMI device (for example, a smart meter or advanced meter).

1.2.7.1 Reversing Device Installations

Use

This procedure enables you to cancel device installations

Prerequisites

You have executed a device installation that you want to cancel.

Procedure

1. Remove the device ( billing-related removal ) from all utility installations for each installation date.

You can find the installation dates under Utilities Industry Device Management Device Installation Installation Structure Rate Data or Utilities Industry Device Management Technology Device.

2. Terminate any device allocations or relationships you have created. 3. Reverse the installation.

The device has now been technically removed.

4. If necessary, perform a stock transfer for the device removed.

To do this, choose Utilities Industry Device Management Technology Device Device Transfer via Serial Numbers or Device General Inventory Management Goods Movement Transfer Posting .

Result

The device installation has been fully reversed. The device now has the status Removed again.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you reverse an installation of an AMI device (for example, a smart meter or advanced meter).

Example

Initial Situation

Device D1 is technically installed at device location DL1 on the 01.01.2000.

A billing related device installation of device D1 is performed at installation 1 (Inst.1) on the first of February 2000. A billing related device installation of the device D1 is performed at installation 2 (Inst.2) on the tenth of February 2000.

( )

Reversing Device Installations:

You want to reverse the device installation. Proceed as follows:

1. Execute a billing-related device removal of device D1 from installation 2 for the tenth of February 2000. You have now reversed the billing-related installation in installation 2.

2. Execute a billing-related device removal of device D1 from installation 1 for the first of February 2000. You have now reversed the billing-related installation in installation 1.

3. Reverse the installation. ( )

1.2.7.2 Reversing Device Removals

Use

This procedure enables you to cancel device removals.

Prerequisites

You have carried out a device removal that you want to reverse.

You must reverse any stock transfers you have carried out. The device must be available. To do this, choose Utilities Industry Device Management Technology Device Device Transfer via Serial Numbers or Device General Inventory Management Goods Movement Transfer Posting .

1. Perform the removal reversal.

The device has now been technically installed.

2. Create any device allocations or relationships you may have terminated. 3. Install the device ( billing-related installation) in all installations on the removal date. 4. You can determine the removal date in the following way:

Go to the Utilities Industry menu and choose Device Management > Installation > Installation Structure > Rate Dates or

Go to the Utilities Industry menu and choose Device Management > Technology > Device in the Removal Date field.

Result

The device removal has been fully reversed (technically and billing-related. The device is installed.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you reverse a removal of an AMI device (for example, a smart meter or advanced meter).

Example

Initial Situation

Device D1 was fully removed on the 10 February 2000; this means both technically removed from device location DL1 and billing-related from installations 1 and 2.

Reversing Device Removals:

You want to reverse the device removal. Proceed as follows:

1. Reverse the technical removal from device location DL1 for the 10 February 2000. ( )

2. Perform a billing-related device installation of device D1 in the installation 1 (Inst.1) forFebruary 10, 2000. 3. Perform a billing-related device installation of device D1 in the installation 2 (Inst.2) February 10, 2000.

( )

1.2.7.3 Reversing Device Replacements

Use

This procedure enables you to reverse device replacements.

Prerequisites

You have carried out a device replacement that you want to reverse.

You must reverse any stock transfers you have carried out. The device must be available. To do this, choose Utilities Industry Device Management Technology Device Device Transfer via Serial Numbers or Device General Inventory Management Goods Movement Transfer Posting .

Procedure

1. Perform a billing-related removal for the installed (replaced) device from all installations on the device replacement date or each installation date. You can determine the installation date via the Utilities Industry menu under: Device Installation Installation Installation Structure Rate Data or

Utilities Industry Device Management Technology Device .

2. Terminate any device allocations or relationships you have created for the newly installed device. 3. Perform the replacement reversal.

The new device is technically removed and the old device is technically installed . 4. Establish any device allocations or register relationships you require for the re-installed device

5. Execute a billing-related installation for the re-installed device in all installations on the device replacement date or on each removal date. 6. Perform a stock transfer for the device removed.

7. Perform a stock transfer for the device removed.

Result

The replacement has been fully reversed. The device now has the status Installed again.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you reverse a replacement of an AMI device (for example, a smart meter or advanced meter).

Example

Initial Situation

Device D1 is technically installed in the device location DL1 on the January 01, 2000.

A billing related device installation of device D1 is performed in installation 1 on February 01, 2000. A billing related device installation of device D1 is performed at installation 2 on February 10, 2000. Replace device D1 with device D2 on March 01, 2000.

This replacement corresponds to a billing-related installation of device D2 on the 01 of March 2000 in device location DL1 and the installations Inst.1 and Inst.2.

( )

This produces the following results for March 01, 2000: ( )

Reversing Device Replacements:

You want to reverse the device replacement. Proceed as follows:

1. Execute a billing-related device removal of device D2 from the Inst.2 installation on March 01, 2000. You have now reversed the billing-related installation of device D2 in the installation Inst.2 on March 01, 2000. 2. Execute a billing-related device removal of device D2 from the Inst.1 installation for March 01, 2000.

You have now reversed the billing-related installation of device D2 in the installation (Inst.) 1 for March 01, 2000. 3. Reverse the device replacement.

( )

This produces the following results for March 01, 2000: ( )

4. Perform a billing-related device installation of device D1 in installation 1 for March 01, 2000. 5. Perform a billing-related device installation of device D1 for March 01, 2000 in installation 2.

( )

1.2.8.1 Device Modification

Purpose

You use this component to enter changes to a device. You can modify warehouse devices and devices installed in the grid. If devices are already installed in the grid, the installation structure is adjusted as necessary.

Implementation considerations

This component is optional. You can use it for resetting device parameters as well as reprogramming, modifying, and reconnecting devices. Examples of modification include:

Changing the register configuration of a device Using a different winding of a transformer

Features

Modification includes the following functions:

Changing the device master data (such as register group or input/output group) Changing set values (such as measured pressure or the command group) Changing device-specific gas data (such as the altitude correction pressure)

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you modify an AMI device (for example, a smart meter or advanced meter).

Use

This function allows you to change device data and register data. This function does not allow you to change device categories, however.

Prerequisites

The contract for the installation of the device must not have been billed before the modification date.

When you enter the modification, the device must not have been modified or changed in the system after the actual modification date. The entry in the system must correspond to the actual history of the processes.

Example

You enter the modification on 10/12. The installation took place on 10/08. A device modification or a change to the device data may not have been entered after 10/08.

Special prerequisites for modification

Activity Prerequisites

Change device data of current time slice The device has undergone technical removal. Change technical data of registers in any time slice The device has undergone technical installation.

Activities

If you have changed technical register data, you must enter meter reading results for the corresponding registers.

To allocate another device category (material) to the device, go to one of the following application components, depending on where the device is managed: Inventory Management (MM-IM)

Plant Maintenance (PM)

If you modify an installed device in the current time slice, you can change the device’s register allocation during the modification.

If parameters such as the measured pressure or the billing factor were changed for a device in a device allocation, the device allocations are adjusted as necessary.

A message is displayed if the automatic adjustment is not possible. You can go directly to the device allocation and check and adjust the attribute manually. To do this, choose Goto Device allocations .

If data of registers in register relationships has changed, you can branch to register relationship maintenance and adjust the data.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you modify an AMI device (for example, a smart meter or advanced meter).

1.2.8.1.1 Entry of Meter Reading Results During Modification

Prerequisites

You have changed the technical register data. Procedure

Choose Utilities industry Device management Meter reading Entry of meter reading results Single entry.

1.2.8.1.2 Allocation of Different Device Category via MM-IM

Prerequisites

The device you wish to modify is maintained in the Inventory Management (MM-IM) application component.

Procedure

1. Choose Logistics Materials management Inventory management. 2. Choose Goods movement Transfer posting

You branch to the screen for entering transfer postings.

3. Enter movement type 309 (transfer posting material to material). You must also enter a storage location and a plant. Chose Continue . You branch to the screen for entering new transfer posting items. Here you can carry out all transfer postings.

Result

A different device category (material) has been allocated to the device.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you change the device category of an AMI device (for example, a smart meter or advanced meter).

1.2.8.1.3 Allocation of Different Device Category via PM

Prerequisites

The device you wish to modify is not maintained in the Inventory Management (MM-IM) application component.

Procedure

1. Choose Logistics Plant maintenance Technical Objects

2. Choose Serial numbers Change and enter the serial number.Chose Continue . 3. Choose Serial data and then Edit Change material no.

The Change material serial number dialog box appears. 4. Enter the new material. Chose Continue .

Note

You may be notified of the system status of the device (piece of equipment). 5. Save your data.

Result

A different device category (material) has been allocated to the device.

Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you change the device category of an AMI device (for example, a smart meter or advanced meter).

1.2.9 Installation Structure

Purpose

You can use this component to manage technical and billing data as well as period consumption of devices. Features

Technical data

Device allocations describe dependencies of devices with other devices, such as meters controlled by ripple control receivers or a group of transformers connected to a meter.

Register relationships describe the relationships between registers. The registers can belong to different contracts. The following relationships are taken into account when creating a meter reading order:

Allocation of active registers to reactive registers for calculating the cosine phi Serial switching of several registers (primary/secondary meter relationships) Linking of registers to different usage types (on-peak/off-peak check) Control relationships

Special relationships for allocating thermal gas factors

Logical registers describe the allocation of a certain task to a register and are most important in device replacement. The register of the old device must have the same logical register number as the register of the new device because

billing data is copied to the new register

the billing component must recognize which register is to take over the role of the old device (especially in the case of demand values) Billing data

Rate data is dependent on the installation and therefore can only be maintained if the device is allocated to an installation. You can maintain rate data such as: The relevance of a register to billing

The rate type of a register The price class Period consumption

The period consumption is used to determine the expected meter reading of a register for a certain date if meter reading results Are not yet available, such as in the case of initial data creation

Cannot be used, for example if there is a change of tenant

Are to be ignored, for example if the customer has a complaint regarding budget billing

Use

This function enables you to allocate devices to one another and store additional attributes.

A distinction is made between controlled devices, such as meters, and controlling devices, such as a transformer switched in series.

Integration

You usually define device allocations on the initial screen for device installation.

The device allocation is terminated if one of the devices undergoes a technical removal, however when you reverse a device removal, any device allocations that were terminated are restored.

Similarly:

if you reverse a device installation, any device allocations that were created are terminated.

If you reverse a device replacement, any device allocations that were created are terminated while any device allocations that were terminated are restored.

Meter Data Unification and Synchronization (MDUS) System Notification for AMI Devices

If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you generate: a new allocation involving an AMI device (for example, a smart meter or advanced meter)

a new allocation involving registers belonging to an AMI device

The system also modifies the MDUS system when you allocate a profile to registers belonging to an AMI meter.

Prerequisites

The devices to be allocated to one another must have undergone a technical installation and have certain characteristics depending on the allocation type. Only water or gas meters or pressure regulators may be part of a pressure regulator allocation. Only meters that measure indirectly can be in a transformer allocation.

Features

Device allocation is historical.

Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice into two slices and maintain them.

Example

Time slice: 01/01/1996 to 12/31/1999 Period already billed: 01/01/1996 to 12/31/1999

The time slice is divided into two time slices: 01/01/96 to 12/31/1996 and 01/01/1997 to 12/31/9999. The unlimited time slice is not in the period billed and therefore can be maintained.

It is also possible to define an allocation without an allocated device in order to store the attributes of the device allocation. For example, measured pressure can be stored in a pressure regulator allocation although the pressure regulators do no exist in the system.

The attributes measured pressure for the pressure regulator allocation or billing factor for transformer allocations are relevant to billing and mandatory for gas meters or meters that do not measure directly.

Device allocations can be defined at the register or device level of the controlled device. Metering devices (meaning devices with registers) are allocated at the register level. Devices without registers are always allocated at the device level. The controlling device is always entirely allocated to the controlled device. It is possible that a controlling device (such as a ripple control receiver) has been replaced during the time slice of the device allocation. In this case, the device that is valid at the beginning of the time slice is displayed. You must also set the TM indicator (device not valid for the entire period). You can double-click on this indicator to display the valid devices with corresponding validity periods. You can also display these devices by selecting the appropriate line and choosing Extras History

It is also possible to define your own allocation types. To do this, you add new entries to the table of allocation types. These allocations are not relevant to billing, however.

Activities

When you maintain billing-relevant device allocations, you must enter meter readings for the devices. In the case of sub-annual changes, you must enter meter readings manually.

1.2.9.1.1 Creating Device Allocations

Prerequisites

The devices have undergone a technical installation. You now wish to maintain device allocations.