SAP IS-U

Industry Solution Utilities

Device Management
Unit 1 Technical Master Data

Unit 2 Technology

Unit 3 Device Installation

Unit 4 Scheduling

Unit 5 Meter Reading

Techincal Master Data

Unit Objectives

At the conclusion of this unit, you will be able to:

• Identify technical master data involved in IS-U

• Identify technical master data relations

Techincal Master Data

Data Model
Techincal Master Data

Data Model

CONTRACT BUSINESS
CONTRACT
ACCOUNT PARTNER

INSTALLATION PREMISE

CONNECTION
OBJECT
PM-FUNCTIONAL LOCATION
DEVICE DEVICE
DEVICE
CATEGORY LOCATION
MM-MATERIAL PM-EQUIPMENT PM-FUNCTIONAL LOCATION

CONNECTION

PM-EQUIPMENT
Techincal Master Data

Connection Object
• Connection object is a building, piece of property or other facility that is
connected to the supply grid
• Has an address that links it to the regional structure
• It is managed as the functional location in PM

Connection
Object
Techincal Master Data

Connection
• Link of the Connection object to the utility company
• The connection is a piece of equipment in Plant Maintenance (PM) application
Techincal Master Data

Premise
• Premise is an enclosed spatial unit that is supplied with utility services, such
as an apartment or a factory.
• Connection object comprises one or more premises
• Allocated to a connection object, has de same address as the connection
object
• Can include several installations to be billed
• Can have several divisions
Techincal Master Data

Device Location
• Device location is an enclosed spatial unit in a connection object where any
number of devices are installed
• Independent of division
• Device location can be assigned to a premise if it applies to that premise only
• Device location corresponds to a functional location in the Plant Maintenance
(PM) application
Techincal Master Data

Utility Installation
• Links technical and business master data
• Is allocated to a premise
• Applies to one division
• Serves as the basis for devices billing
• Utility installation is linked .............. to billing via the rate category
..... to scheduling via the meter reading unit
..... to reginal structure via the premise
..... to a business partner during the move-in
Techincal Master Data

Utility Installation Enviroment

BUSINESS
PARTNER
Business
Master Data
Regional CONTRACT
Structure ACCOUNT
Scheduling

CONTRACT PORTION

Postal Regional Structure

STREET SECTION METER READING

CITY STREET INSTALLATION
UNIT

DEVICE
PREMISE
LOCATION

POLITICAL COMPANY
CONNECTION
STRUCTURE STRUCTURE
OBJECT
Technical
Master Data
Techincal Master Data

Utility Installation History

Installation 10001

01/01/90 - 14/08/1992 Terminated Contract 10000001

15/08/92 - 31/03/1993 No Contract Allocated

01/04/93 - 14/04/1997 Terminated Contract 10000002

15/04/97 - 12/31/9999 Current Contract 10000003

Techincal Master Data

Utility Installation History (Time Slices)

01/08/2002

Customer
Contract 1 1 Move-Out Move-In Customer
Contract 2 1

Contract
Contract 1 1 Contract
Contract 2 1

Installation
Installation

Time Slice 1: Time Slice 2:

15/04/97- 31/07/02 Beginning 01/08/02

Contract
Contract11 Contract
Contract22
R

May 1 June 1 July 1 Aug. 1 Sept. 1 Oct. 1 Dec. 1

Techincal Master Data

Utility Installation Time Slices: Time-Based Data

l Time-based data enables you to take any changes in the data

into account. In the billing, for example, rate category can be
changed within the billing period.
l Prior to changing time-based data you must insert a
new time slice.
l Time-based data vs Non time-based data
n Billing class n Base period category
n Rate category n Meter reading type control
n Industry sector n Blocking reason
n Temperature area (Control of billing / meter reading)
n Exemption from franchise fee n Guarantee of supply
n Meter reading unit
Contents

Unit 1 Technical Master Data

Unit 2 Technology

Unit 3 Device Installation

Unit 4 Scheduling

Unit 5 Meter Reading

Technology

Unit Objectives

At the conclusion of this unit, you will be able to:

• Map device technology in IS-U, and identify the

standard components used for this purpose

• Identify the relation between the material and the

device category, or between the piece of equipment
and the device

• Identify the elements that comprise a device

category, and state what you need to bear in mind
when creating device categories
Technology

Basic Device Category - Device Category - Device

Basic Device
Category
for example, meter METER

(n:1)
Device Category
for example, double-rate
meter
Meter I Meter II Meter III

(n:1)

071 61 92

0 539 802
0 716 192

125.256.01 071 61 92
053 98 02

125.256.01
0 539 802
II.1 II.2 II.3 II.n
Devices 125.256.01

0 716 192
071 61 92

053 98 02
0 539 802

125.256.01
125.256.01
Technology

Basic Device Category

l Groups devices that have the same technical properties

l Basic device categories:

 Meters (measure consumption-dependent resources (that is, electricity, gas, water,
heating))
 Transformers (voltage transformers, current transformers)
 ARCRs (audio frequency ripple control receivers transmit information across the grid,
for example, to control switching of rates in the case of off-peak storage heaters)
 Remote meters (enter consumption values over distances, for example meters that can
be read via modem)
 Counters (determine the heat quantity issued for district heating)
 Correctors (determine the standard cubic meters consumed on the basis of the
technical gas value temperature, pressure and compressibility)
 Pressure regulators (adjust the gas pressure)
 Sensors (transmit pulses, for example, temperature probe)
 Containers and Vehicles (required for waste disposal)
Technology

Basic Device Categories - Customizing

l Define which basic device categories are allowed for each division
category
l Define combinations of basic device categories

l Define how basic device categories are sorted

 For device category processing
 In the replacement and notification worklist group

l Define texts for basic device categories

Technology

Device Category - Device

• Serial number:
Sie-970701-503
• Manufacturer: Siemens
• Production year: 2000
• Valid from 01.07.2000

• Serial number:
AEG-980101-125
• Manufacturer: AEG
• Production year: 2002
• Valid from 01.01.2002

• Serial number:
LGY-980701-300
• Manufacturer Landis&Gyr
• Single-rate meter that is subject to certification :
• Production year: 2002
• Plastic housing and external seal • Valid from 01.07.2002

• Six pre-decimal places, one decimal place

Device Category Device

Technology

Device Category
l Is classified by the basic device category
l Can also be a combination of different basic device categories
l Includes information relevant for billing as well as information for device certification
and inspection
l Corresponds to the material in the logistics component

DEVICE
CATEGORY

MM data IS-U data

Technology

Creating Device Categories with a Reference Material

Technology

Creating Device Categories without a Reference Material

Technology

Technical Groups for Device Category

l Technical groups can only be

allocated to device categories REGISTER GROUP DEVICE CATEGORY INPUT/OUTPUT GROUP
belonging to certain basic
device categories

COMMAND WINDING GROUP

GROUP
Technology

Technical Groups for Device Category – Register Group

l Registers:
 Measure consumption and energy
 Can exist physically or as a display in electronic devices
l Register Group:
 Groups together the registers of a device
 Can cover several divisions categories
 Can be assigned to several device categories
 Reference register relationship
 Register group data is merely default data and values can be changed as pleased
during an installation or modification

REGISTER
Technology

Device

l Is an instrument used for measuring consumption, processing data or

controlling and protecting other instruments
l Devices are identified using material and serial numbers, and are managed
in the Plant Maintenance (PM) application as pieces of equipment.

DEVICE

PM data IS-U data

Technology

Device - Customizing

l Define IS-U equipment categories

l Allocate class type to IS-U equipment categories

Technology

Device Category Data vs Device Data

Material
Description
SIE-DTZ 0815

Register Register
Group

Meter
reading
Device Category
Data
Device Number Device Data
(Serial Number)
Technology

Numbers in Device Management

Technology

Summary

l IS-U/CCS is integrated with the standard components Logistics-Materials

Management (LO-MM) and Logistics-Plant Maintenance (LO-PM) via the
Device Category (= Material) and the Device (= Equipment)

l Device Categories are based on predefined basic device categories and

definethe technical device data. Additionally, there is information stored in the
device category, which is relevant to billing as well as information on device
inspection and certification

l Devices are uniquely identified by the combination of their material no. (LO-
MM component) and serial no. (LO-PM component). The history of a device
can be look up using process data. Location data enables spatial allocation
of the device, whereas plant maintenance data contains information on the
allocated PM-planning plant
Contents

Unit 1 Technical Master Data

Unit 2 Technology

Unit 3 Device Installation

Unit 4 Scheduling

Unit 5 Meter Reading

Device Installation

Unit Objectives

At the conclusion of this unit, you will be able to:

• Perform technical and billing-related installation,

removal and replacement of devices in the system

• Describe the utility installation structure and change

the rate data and technical data of installed devices

• Map device relationships

• Describe the customizing activities required

Device Installation

Device Installation Functions

l Installation, removal, and replacement of devices from a:

n Technical point of view: linking a device to a device location
(1:1 relationship)
n Billing point of view: linking a device to a utility installation
(1:n relationship)

l Creation of device groups

l Changes to rate data and technical data of devices that

have already been installed (utility installation structure)

R
Device Installation

Device Group

Group of devices that comprise a logical unit

Examples of device groups:

A
B l Transformer groups are made up of
current and voltage transformers linked
to each other. Transformer groups have
C a single transformation ratio.

l Two integrated water meters installed

together. These meters measure
consumption separately. The
consumption from these meters can be
Device
DeviceGroup
Group shown separately on the bill, but is
usually billed together

In this way, devices that belong together to a device group cannot accidentally
be removed or installed separately. Any replacement has to be expressly confirmed
Device Installation

Device Group - Customizing

l Define group types of your own

l Assign group types to the following predefined group types:

 Integrated water meter
 Transformer group
 Measurement panel
 Other

l Restrict group types to specific divisions

Device Installation

Types of Device Installation (I)

Device Installation

Types of Device Installation (II)

Device Installation

Fields Relevant to Installation

Device Installation

Installation - Period Consumption

Device Installation

Installation - Customizing

Inst.Div. Div.Low Div.Upper Incl./Excl. Option

01 01 02 I BT
03 03 I EQ
05 07 E EQ
Device Installation

Device Removal
Device Installation

Device Removal
Device Installation

Device Installation - Customizing

Device Installation

Reversal of Installation / Removal / Replacement

Device Installation

The Utility Installation Structure

Device Installation

Summary

Installation: Unit Summary 1

 Installing devices in a utility installation links technical and business

master data. The device location corresponds to a functional location
in the Plant Maintenance (LO-PM) application component.

 Devices can be installed either in one step (Installation relevant to all

data) or in two steps (first technical, then billing-related installation).

 When a device is removed, technical and billing-related data is

deleted. However, the data can still be tracked.


 SAP
SAP
SAP AG
AG
AG
Installation: Unit Summary 2

 During device replacement, a device is replaced with a device of the

same device category (or a device similar in function).

 The installation structure describes the devices installed in the utility

installation from a technical point of view(device allocations and
register relationships) and a billing point of view (rate type and price
class).
 You can model various installation services (for example, service
connection) in IS-U/CCS using the Sales (SD) application component
and the IS-U component Work Management (WMS)


 SAP
SAP
SAP AG
AG
AG
Contents

Unit 1 Technical Master Data

Unit 2 Technology

Unit 3 Device Installation

Unit 4 Scheduling

Unit 5 Meter Reading

Scheduling

Unit Objectives

At the conclusion of this unit, you will be able to:

• Structure your supply area according to meter

reading or billing criteria

• Explain the terms portion, meter reading unit and the

roles they play in scheduling

• Model and update meter reading and billing dates in

the system
Scheduling

l Used for planning and controlling the following functions:

n Meter reading order creation
n Billing

l Generates periodic dates (schedule records) for:

n Meter reading

n Billing

l To generate schedule records, you require:

n Schedule master records for meter reading
(meter reading units)
R

n Schedule master records for billing (portions)

Scheduling

Portion

l Portions group together contracts that are to be billed

together

l They contain schedule master records for billing

l You can allocate a contract to a portion in either of the

following ways:
n Indirectly via the meter reading units defined in the installation
that corresponds to the contract
n Directly in the contract
Scheduling

Meter Reading Unit

l Meter reading units group together - according to regional

criteria - installations that are to be read on a certain date.

l The schedule master records for meter reading units contain

all data relevant to meter reading scheduling.

l Meter reading units can only be created if a portion already

exists.

l Several meter reading units can be allocated to one portion.

l Meter reading units form the basis for device management.

Scheduling

Portions & Meter Reading Units

Scheduling

Generation of Schedule Records

Schedule Master Records Schedule Records

PORTION-A 02/2003

PORTION-A PORTION-A 04/2003

PORTION-A 06/2003

Generation of
Schedule Records
MRU-A 02/2003

MRU-A MRU-A 04/2003

MRU-A 06/2003
Scheduling

Annual Billing

2002 2003
Scheduling

Monthly Billing

27. 28. 29. 30. 31. 1. 2. 3.

July August
27. 28. 29. 30. 31. 1. 2. 3. 27. 28. 29. 30. 31. 1. 2. 3.
Scheduling

Summary

l The scheduling component is used for generating dates periodically

for meter reading, billing and budget billing control.

l Portions group together contracts that are to be billed jointly.

l Meter reading units group together installations that are to be read on

a certain date.

l The generation of dates is based on schedule master data either for

billing or meter reading. The schedule master records for billing are
stored in the portion, and those for meter reading are stored in the
meter reading unit.
Contents

Unit 1 Technical Master Data

Unit 2 Technology

Unit 3 Device Installation

Unit 4 Scheduling

Unit 5 Meter Reading

Meter Reading

Unit Objectives

At the conclusion of this unit, you will be able to:

• Name the different reasons for taking meter readings

• Establish the route for the meter reader

• Create, output and monitor meter reading orders

• Enter meter reading results, and validate them using

extrapolation and weighting procedures
• Correct, estimate and reverse meter reading results

• Name the customizing activities you can carry out in

the IMG
Meter Reading

Meter Reading Overview

Meter reading
order creation

Meter reading order Billing order

Order Output

Meter reading Download

documents Meter
reading Billing
Upload results
Entry
Fast/Single
entry Verification

Correction
Meter Reading

Meter Reading Reasons

l Periodic meter reading (based on schedule records)

l Aperiodic meter reading, such as:

n Interim meter reading with or without billing
n Service territory transfer with billing
n Control reading

l Meter reading resulting from a process, such as:

n Customer move-in
n Device removal
Meter Reading

Meter Reading / Billing Order

Meter Reading Order Billing Order

l Is the prerequisite for a meter reading l Is the prerequisite for billing

l Displays all data required for the meter l Is created in addition to meter reading
reading, such as: order if a meter reading is relevant for
n Meter reader
billing (e.g. periodic meter readings)

n Date l Is also created for flat-rate installations

n Address
n Expected meter reading
l Contains data for billing, for example:

l Can be printed or transferred to external n Target billing date

entry systems (for example, MDE n Portion
device) n Installation
n Status
l Used for monitoring (for example,
tracking)
Meter Reading

Meter Reading Order Data

Data Specific to Entry Time-Based Data

• Target reading date
• Entry number
• Target billing date
• Check number
• Meter reading reason
• Planned meter reading
• Meter reader
• Control group
• MDE number Meter
Reading
Order Meter Reading Data
• Expected meter reading
• Expected consumption
• Upper limit of meter
reading

Data Environment
Meter Reading

Meter Reading Order Creation

Meter Reading

Meter Reading Order Creation - Interval Check

Meter Reading

Mass Order – Background job

Meter Reading

Downloading and Uploading Meter Reading Orders

Meter Reading

Download

l Uses the Raw Data Interface (RDI) from SAP script

l Spool: transfer to a spool or file (depending on customizing

settings)

l IDoc interface (intermediate document): used for electronic data

interchange (EDI) between different computers and systems.
SAP standard format for electronic data exchange
Meter Reading

Meter Reading Organization - Street Route

l Shows the order meter reader reads devices from a Meter

Reading Unit
Meter
Reading City District 1
Unit A

Street 1 St r
ee
tR
Connection ou
te
Street 2 Object 1

Connection Device
Street n Object 2 Location 1

Connection Device Device 1

City District 2 Object n Location 2
Device
Location n Device 2
City District n
Device n

l Possibility of monitoring whether there are unassigned

devices to meter reading sequence
Meter Reading

Manual Monitoring

l Monitoring at the level of meter reading unit, installation,

device, business partner, …

l Monitoring of:
n Schedule records
n Meter reading orders
n Billing orders
n Meter reading results

l Gives information about:

n Status
n Meter reading reason
n Validation
n Meter reading date

l Go directly to device, contract, meter reading order …

Meter Reading

Automatic Monitoring

l Automatic monitoring of missing and implausible meter

reading results

l Follow up actions are started after specific periods depending

on status, meter reading reason and meter reading type

l Follow up actions are defined in SAP enhancements

l If a (further) follow up action is not defined, the result is

estimated automatically

l Automatic monitoring is started in the IS-U menu

Status 0 01/01: planned reading by customer

Status 1 05/01: reminder User-defined
Status 2 09/01: meter read by utility company follow-up actions
Status 3 15/01: Automatic estimation
Meter Reading

Entry of Meter Reading Results

l Mass entry for periodic meter readings

n Prerequisite: meter reading order creation
n Automatic: Upload using the standard transaction IDoc Type and EDI Basis
n Manual: fast entry
w Without correction: implausible values are reset
w With correction: validation is possible
l Single entry
n Is possible without previous creation of meter reading order
n Used, for example, in the case of interim and control readings

Meter reading results uploaded

List of meter reading results

Status: Plausible Status: Implausible Status: Error

Meter Reading Correction Single Entry

Result (Only possible if data can be
recognized)
Meter Reading

Meter Reader Notes

Meter Reading

Validation
l Each meter reading result is checked for plausibility (validated)

Implausible

Correction

Meter reading
Validation Plausible
result

l Fixed validations are performed automatically

n Validation of previous meter reading (is the previous meter reading plausible?)
n Validation of fixed-value deviation (No consumption for inactive or blocked
installations?)
l In customizing is possible to define:
n Validation classes (contain a pool of all possible validations of a rate)
n Configurable validations (zero consumption, repeated costumer reading/estimation..)
n Tolerance limits (positive/negative deviation, error class, …)
n User-defined validations (SAP enhancement)
Meter Reading

Extrapolation of Expected Consumption

Meter Reading

Extrapolation Using Meter Reading Results

l Prerequisite: the actual meter reading result must best

reflect the consumption pattern in period

Rate
Minimum
Weighting
Percentage
Procedure
Portion

Actual
Actual Expected
Expected
Meter
Meter Meter
Meter
Extrapolation
Reading
Reading Reading
Reading
Result
Result Result
Result
Installation Base
Period
Category
Meter Reading

Weighting

l Determination of expected values (meter readings for example)

by means of:

n
n

n
Meter Reading

Extrapolation Example
Meter Reading

Correction
l Correction on:
n Implausible results upon entry
n Implausible, reset results
n Plausible results
l Is it possible to:
n Correct the results
n Release the results without correction
n Reset the results
n Estimate the results
n Create correction order

l In the correction screen following data is available:

n Meter reading data
w Current meter reading and consumption
w Previous meter reading
n Forecast and validation data
w Forecast period
w Expected values
w Source of the forecast period (previous period, period consumption, …)
n Device data
Meter Reading

Automatic Estimation

l You can select meter reading results, for example, according

to:
n Meter reading unit
n Business partner
n Device
n Planned meter reading dates

l In customizing it is possible to define:

n Should the meter reading result be overestimated?
n Enhancement for user own estimation is triggered?
Meter Reading

Reversal

l Is it possible to select an entry for reversal by:

n Meter Reading Unit n Device
n Contract n Planned meter reading date
n Installation n Meter reading reason

l Following objects are deleted during the reversal

process (if they exist):
n Meter Reading Order
n Billing Order
n Meter Reading Result (under petition)
Meter Reading

Summary

l The street route and scheduling form the basis for periodic
meter readings
l It is possible to perform meter reading others than for periodic
meter reading (is the case of interim or control meter readings)
l During meter reading order creation, meter reading order is
generated and if the reading is relevant to billing, a billing order
too.
l The meter reading order contain all of the data required for
meter reading. It can be printed or passed to external entry
systems.
l Meter reading results are validated when they are entered.
Extrapolations are used in the validation process.
l It is possible to monitor and reverse meter readings
l It is possible to correct and estimate meter reading results