device_management.ppt

7/27/2019 DEVICE_MANAGEMENT.ppt

1/82

SAP IS-U/CCSIndustry Solution Utilities / Customer Care & Service System

Device Management


2/82

Agenda

Day 1

Mon, February 10Overview

Customer Service

Day 2

Customer Service

Day 3

Device Management

Tue, February 11

Wed, February 12

Day 4

Device Management

Day 5

Work Management

Thu, February 13

Fri, February 14

Day 6

Mon, February 17Work Management

Migration Workbench

Day 7

Migration Workbench

Day 8

Workflow

Tue, February 18

Wed, February 19

Day 9

Billing & Invoicing

Day 10

Billing & invoicing

Thu, February 20

Fri, February 21

Day 11

Mon, February 24FI-CA

Day 12

FI-CA

Day 13

FI-CA

Tue, February 25

Wed, February 26


3/82

Unit 4 Scheduling

Unit 1 Technical Master Data

Unit 3 Device Installation

Meter ReadingUnit 5

Unit 2 Technology

Contents


4/82

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

Unit Objectives

Identify technical master data involved in IS-U

Identify integration between IS-U and Logistics

application component

Techincal Master Data

Identify technical master data relations


5/82


Data Model


6/82

Data Model and Integration with Logistics

CONTRACT

PM-EQUIPMENT

CONNECTION

PM-FUNCTIONAL

LOCATION

CONNECTION

OBJECT

INSTALLATION PREMISE

Integration with logistics

PM-FUNCTIONALLOCATION

DEVICE

LOCATIONDEVICE

PM-EQUIPMENT

DEVICE

CATEGORY

MM-MATERIAL


CONTRACT

ACCOUNT

BUSINESS

PARTNER


7/82

Connection Object


Connection object is a building, piece of property or other facility that isconnected to the supply grid

Has an address that links it to the regional structureIt is managed as the functional location in PM

Connection

Object


8/82

Connection


Link of the Connection object to the utility companyThe connection is a piece of equipment in Plant Maintenance (PM) application


9/82

Premise


Premise is an enclosed spatial unit that is supplied with utility services, suchas an apartment or a factory.

Connection object comprises one or more premisesAllocated to a connection object, has de same address as the connection

object

Can include several installations to be billedCan have several divisions


10/82

Device Location


Device location is an enclosed spatial unit in a connection object where anynumber of devices are installed

Independent of divisionDevice location can be assigned to a premise if it applies to that premise onlyDevice location corresponds to a functional location in the Plant Maintenance

(PM) application


11/82

Utility Installation


Links technical and business master data

Is allocated to a premiseApplies to one divisionServes as the basis for devices billingUtility 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


12/82

Utility Installation Enviroment


DEVICE

LOCATIONPREMISE

CONNECTION

OBJECT

INSTALLATION

CONTRACT

CONTRACT

ACCOUNT

BUSINESS

PARTNER

PORTION

METER

READING UNIT

Scheduling

Technical

Master Data

Business

Master Data

POLITICAL

STRUCTURE

COMPANY

STRUCTURE

CITY STREETSTREET

SECTION

Postal Regional Structure

Regional

Structure


13/82

Installation 10001

Current Contract 10000003

Terminated Contract 10000002

No Contract Allocated

Terminated Contract 10000001

15/04/97 - 12/31/9999

01/01/90 - 14/08/1992

15/08/92 - 31/03/1993

01/04/93 - 14/04/1997

Utility Installation History



14/82

R

Contract 1Contract 1

Installation


Time Slice 1:

15/04/97- 31/07/02

Time Slice 2:

Beginning 01/08/02

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



Move-Out Move-InContract 1Customer 1 Contract 1Customer 2

Installation

01/08/2002

Utility Installation History (Time Slices)



15/82

l Time-based data enables you to take any changes in the datainto 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 anew time slice.

l Time-based data

n Billing class

n Rate category

n Industry sector

n Temperature area

n Exemption from franchise fee

n Meter reading unit

Utility Installation Time Slices: Time-Based Data


Non time-based datavs

n Base period category

n Meter reading type control

n Blocking reason

(Control of billing / meter reading)

n Guarantee of supply


16/82

Unit 4 Scheduling



Meter ReadingUnit 5

Unit 2 Technology

Contents


17/82


Unit Objectives

Map device technology in IS-U, and identify the

standard R/3 components used for this purpose

Identify the relation between the material and the

device category, or between the piece of equipment

and the device

Technology

Identify the elements that comprise a devicecategory, and state what you need to bear in mind

when creating device categories


18/82

Basic DeviceCategory

for example, meter

Devices

0539802

125.256.01

07161920539802

125.256.01

0716192

0539802

125.256.01

0716192

0539802

125.256.01

0716192

0539802

125.256.01

0716192

Device Categoryfor example, double-ratemeter

METER

Meter I Meter III

II.2II.1 II.n

Meter II

Basic Device Category - Device Category - Device

Technology

(n:1)

(n:1)

II.3


19/82

Basic Device Category

Technology

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 technicalgas 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)


20/82

Technology

l Define which basic device categories are allowed for each division

category

Basic Device Categories - Customizing

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


21/82

Single-rate meter that is subject to certification

Plastic housing and external seal

Six pre-decimal places, one decimal place

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


Serial number:LGY-980701-300

ManufacturerLandis&Gyr

:Production year: 2002


Technology

Device Category - Device

Device Category Device


22/82

Technology

Device Category

IS-U dataMM data

l Is classified by the basic device category

l Corresponds to the material in the logistics component

l Includes information relevant for billing as well as information for device certification

and inspection

DEVICE

CATEGORY

l Can also be a combination of different basic device categories


23/82

Technology

Creating Device Categories with a Reference Material


24/82

Technology

Creating Device Categories without a Reference Material


25/82

Technology

Technical Groups for Device Category

WINDING

GROUP

COMMAND

GROUP

DEVICE

CATEGORY

INPUT/OUTPUT

GROUP

REGISTER

GROUP

l Technical groups can only beallocated to device categories

belonging to certain basic

device categories

T h l


26/82

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

T h l


27/82

Technology

Device

l Is an instrument used for measuring consumption, processing data orcontrolling 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.

IS-U dataPM data

DEVICE

T h l


28/82

Technology

l Define IS-U equipment categories

Device - Customizing

l Allocate class type to IS-U equipment categories

T h l


29/82

SIE-DTZ 0815

Register

Group Register

Description

Device Number(Serial Number)

Device Data

Device Category

Data

Meter

reading

Material

Technology

Device Category Data vs Device Data

T h l


30/82

Technology

Numbers in Device Management

T h l


31/82

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 thedevice category, which is relevant to billing as well as information on device

inspection and certification

l Devices are uniquely identified by the combination of theirmaterial 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 theallocated PM-planning plant

Technology

Summary

Contents


32/82

Unit 4 Scheduling



Meter ReadingUnit 5

Unit 2 Technology

Contents

Device Installation


33/82


Describe the utility installation structure and change

the rate data and technical data of installed devices

Perform technical and billing-related installation,

removal and replacement of devices in the system

Map device relationships

Unit Objectives

Device Installation

Describe the customizing activities required

Device Installation


34/82

Device Installation Functions

Device Installation

l Creation of device groups

R

l Changes to rate data and technical data of devices thathave already been installed (utility installation structure)

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)

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

Device Installation


35/82

Device Installation

Group of devices that comprise a logical unit

Device GroupDevice Group

AB

C

Examples of device groups:

l Transformer groups are made up of

current and voltage transformers linkedto each other. Transformer groups have

a single transformation ratio.

l Two integrated water meters installed

together. These meters measure

consumption separately. The

consumption from these meters can beshown separately on the bill, but is

usually billed together

Device Group

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


36/82

l Define group types of your own

Device Group - Customizing

Device Installation

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


37/82

Types of Device Installation (I)

Device Installation

Device Installation


38/82

Types of Device Installation (II)

Device Installation

Device Installation


39/82

Fields Relevant to Installation

Device Installation

Device Installation


40/82

Installation - Period Consumption

Device Installation

Device Installation


41/82

Installation - Customizing

Device Installation

Inst.Div.

01

03

05

Div.Low

01

03

07

Div.Upper

02

Incl./Excl.

I

I

E

Option

BT

EQ

EQ

Device Installation


42/82

Device Removal

Device Installation

Device Installation


43/82

Device Removal

Device Installation

Device Installation


44/82

Device Installation - Customizing

Device Installation

Device Installation


45/82

Reversal of Installation / Removal / Replacement

Device Installation

Device Installation


46/82

The Utility Installation Structure

Device Installation

Device Installation


47/82

Device Installation

Summary

l Installing devices in a utility installation links technical and business

master data. The device location corresponds to a functional location

in the P lan t Ma in t enanc e(LO-PM) application component.

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

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

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

deleted. However, the data can still be tracked.

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

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

Contents


48/82

Unit 4 Scheduling



Meter ReadingUnit 5

Unit 2 Technology

Contents

Scheduling


49/82


Explain the terms portion, meter reading unit and the

roles they play in scheduling

Structure your supply area according to meter

reading or billing criteria

Model and update meter reading and billing dates in

the system

Unit Objectives

g

Scheduling


50/82

l Generates periodic dates (schedule records) for:

n Meter reading

n Billing

R

l To generate schedule records, you require:

n Schedule master records for meter reading

(meter reading units)

n Schedule master records for billing (portions)

n Meter reading order creation

n Billing

Used for planning and controlling the following functions:l

g

Scheduling


51/82

l Portions group together contracts that are to be billedtogether

l They contain schedule master records for billing

l You can allocate a contract to a portion in either of thefollowing ways:

n Indirectly via the meter reading units defined in the installation

that corresponds to the contract

n Directly in the contract

Portion

g

Scheduling


52/82

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.

Meter Reading Unit

g

Scheduling


53/82

Portions & Meter Reading Units

g

Scheduling


54/82

PORTION-A

MRU-A

PORTION-A 02/2003

PORTION-A 04/2003

PORTION-A 06/2003

MRU-A 02/2003

MRU-A 04/2003

MRU-A 06/2003

Schedule Master Records Schedule Records

Generation of

Schedule Records

g

Generation of Schedule Records

Scheduling


55/82

2002 2003

Annual Billing

g

Scheduling


56/82

July August

Monthly Billing

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

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

Scheduling


57/82

l The scheduling component is used for generating dates periodically

for meter reading, billing and budget billing control.

ll Portions group togethercontracts that are to be billed jointly.

l

l Meter reading units group togetherinstallations 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.

Summary

Contents


58/82

Unit 4 Scheduling



Meter ReadingUnit 5

Unit 2 Technology

Meter Reading


59/82


Name the different reasons for taking meter readings

Unit Objectives

Establish the route for the meter readerCreate, output and monitor meter reading ordersEnter meter reading results, and validate them using

extrapolation and weighting procedures

Correct, estimate and reverse meter reading resultsName the customizing activities you can carry out in

the IMG

Meter Reading


60/82

Meter Reading Overview

Meter reading order Billing order

Meter reading

order creation

Order Output

Entry

Verification

Billing

Correction

Meter reading

documents

Download

Fast/Single

entry

Upload

Meter

reading

results

Meter Reading


61/82

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


62/82

Meter Reading / Billing Order

l Is the prerequisite for a meter reading

l Displays all data required for the meter

reading, such as:

n Meter reader

n Date

n Address

n Expected meter reading

l Can be printed or transferred to external

entry systems (for example, MDE

device)

l Used for monitoring (for example,

tracking)

Meter Reading Order

l Is the prerequisite for billing

l Is created in addition to meter reading

order if a meter reading is relevant for

billing (e.g. periodic meter readings)

n Target billing date

n Portion

n Installation

l Contains data for billing, for example:

Billing Order

n Status

l Is also created for flat-rate installations

Meter Reading


63/82

Meter Reading Order Data

MeterReading

Order

Data Environment

Entry number

Check number

Meter reading reason

Planned meter reading

Meter reader

Control group

MDE number

Meter Reading Data

Data Specific to Entry

Expected meter reading

Expected consumption

Upper limit of meter

reading

Time-Based Data

Target reading date

Target billing date

Meter Reading


64/82

Meter Reading Order Creation

Meter Reading


65/82

Meter Reading Order Creation - Interval Check

Meter Reading


66/82

Mass Order Background job

Meter Reading


67/82

Downloading and Uploading Meter Reading Orders

Meter Reading


68/82

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 datainterchange (EDI) between different computers and systems.

SAP standard format for electronic data exchange

Meter Reading


69/82

Meter Reading Organization - Street Route

l

Shows the order meter reader reads devices from a Meter

Reading Unit

Device n

Device 2

Device 1

Device

Location n

Device

Location 2

Device

Location 1

Connection

Object n

Connection

Object 2

ConnectionObject 1

Meter

Reading

Unit A

Street 1

Street 2

Street n

City District 2

City District n

City District 1

l Possibility of monitoring whether there are unassigned

devices to meter reading sequence

Meter Reading


70/82

Manual Monitoring

l Monitoring at the level of meter reading unit, installation,device, business partner,

l Monitoring of:

ln Statusn Meter reading reasonn Validationn Meter reading date

Gives information about:

n Schedule recordsn Meter reading ordersn Billing ordersn Meter reading results

l Go directly to device, contract, meter reading order

Meter Reading


71/82

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

Automatic Monitoring

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

01/01: planned reading by customer

15/01: Automatic estimation

05/01: reminder

09/01: meter read by utility company

User-defined

follow-up actions

Status 0

Status 1

Status 3

Status 2

Meter Reading


72/82

Entry of Meter Reading Results

l Mass entry for periodic meter readings

n Prerequisite: meter reading order creation

n Automatic: Uploadusing the standard transaction IDoc Type and EDI Basis

n Manual: fast entry

w Without correction: implausible values are resetw 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

Status: Plausible Status: Implausible Status: Error

Meter Reading

Result

Correction Single Entry

Meter reading results uploaded

List of meter reading results

(Only possible if data can be

recognized)

Meter Reading


73/82

Meter Reader Notes

Meter Reading


74/82

Validation

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

Meter reading

result Validation Plausible

Implausible

Correction

l Fixed validations are performed automatically

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 Validation of previous meter reading (is the previous meter reading plausible?)

n Validation of fixed-value deviation (No consumption for inactive or blocked

installations?)

n User-defined validations (SAP enhancement)

Meter Reading


75/82

Extrapolation of Expected Consumption

Meter Reading


76/82

Extrapolation Using Meter Reading Results

l Prerequisite: the actual meter reading result must best

reflect the consumption pattern in period

Actual

Meter

Reading

Result

Actual

Meter

Reading

Result

Minimum

Percentage

Portion

WeightingProcedure

Base

Period

Category

Rate

Installation

ExtrapolationExtrapolation

Expected

Meter

Reading

Result

Expected

Meter

Reading

Result

Meter Reading


77/82

Weighting

Determination of expected values (meter readings for example)

by means of:

l

n

n

n

n

n

Meter Reading


78/82

Extrapolation Example

Meter Reading


79/82

Correction

l Correction on:

n Implausible results upon entryn Implausible, reset resultsn Plausible results

l Is it possible to:

n Correct the resultsn Release the results without correctionn Reset the resultsn Estimate the resultsn Create correction order

l In the correction screen following data is available:

n Meter reading data

w Current meter reading and consumptionw Previous meter reading

n Forecast and validation data

w Forecast periodw Expected valuesw Source of the forecast period (previous period, period consumption, )

n Device data

Meter Reading


80/82

Automatic Estimation

l You can select meter reading results, for example, accordingto:

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


81/82

Reversal

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

n Meter Reading Unit

n Contract

n Installation

l Following objects are deleted during the reversalprocess (if they exist):

n Device

n

n

Planned meter reading date

Meter reading reason

n Meter Reading Order

n Billing Order

n Meter Reading Result (under petition)

Meter Reading


82/82

Summary

l The street route and scheduling form the basis for periodicmeter 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 ordertoo.

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

device_management.ppt

Documents