Download PPT - CIMug

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
Transcript
The Standards Based Integration
Company
Systems Integration Specialists Company, Inc.
61968 – 9 Meter Reading
and Control
CIM University
CESI/TERNA
Milan, Italy
June 15, 2010
Margaret Goodrich, Manager, Systems Engineering
SISCO, Inc.
6605 19½ Mile Road
Sterling Heights, MI 48314 USA
Tel:
+1-903-477-7176
Fax:
+1-903-489-0063
E-Mail:
[email protected]
© Copyright 2010 SISCO, Inc.
Introduction
Scope/Purpose
 Reference Model
 Information Models
 Meter Reading and Control Messages

2
© Copyright 2010 SISCO, Inc.
Scope/Purpose



To Define the exchange of information between a
Metering System and other systems within the Utility
enterprise
Specifies the information content of a set of message
types that can be used to support many of the
business functions related to Merter Reading and
Control.
Typical uses of the message types include:
 Meter Reading and Meter Control
 Meter Events
 Customer Data Synchronization and Customer Switching
3
© Copyright 2010 SISCO, Inc.
Reference Model



The Reference Model provides examples of the logical
components and data flows related to this standard.
The Meter is treated as an “end device”
An End Device:
 Has a unique identity
 Is managed as a physical asset
 May issue events
 May receive control requests
 May collect and report measured values
 May participate in utility business processes

4
The Reference Model describes the flows between the
components.
© Copyright 2010 SISCO, Inc.
Reference Model - Full
5
© Copyright 2010 SISCO, Inc.
Reference Model - Partial
Interface and protocol details of the
Service Point are outside the scope of
IEC 61968-9
Service
Point
Meter
Administration
Scheduled
Read
Readings, events
and status
Data Collection
Scheduled
Read
Meter
Data
Management
Scheduled
Read
Metering System
Tokens
Controls and signals
Control and
Reconfiguration
Peak
Price (1)
Peak
Price (1)
Load
Reduction
Load
Reduction
Network
Operations
Exchange
Portal
Peak
Price
(1)
Scheduled
Read
61968-3
Peak
Price
(2)
61968 Part 9
Customer
Information
and
Billing
61968-8
Defined by other 61968 Parts
Key
6
Outside the scope of 61968
© Copyright 2010 SISCO, Inc.
Reference Model

The reference architecture reflects fine main logical
components related to metering:
 Metering System including data collection, control and
reconfiguration functionality
 Meter Data Management
 Meter Maintenance
 Load Management including load control and load analysis
functionality
 Meter Asset Management
 Meter Administration Functions, which may be a part of the
Meter Data Management
7
© Copyright 2010 SISCO, Inc.
Reference Model
Business Functions
Business
Sub-Functions
Meter Reading and Control (MR)
Metering System (MS)
Abstract Components
Data collection
End point controls
End point reconfiguration
Disconnect/reconnect
Demand reset
On request read
Point of sale
Outage detection and restoration verification
Power reliability and quality events
Metering system events
Meter Maintenance and Asset Management
End point install, configure, remove, repair, disconnect, reconnect
End point asset history
End point reconfiguration
Special read
Meter service request
Tariffs
Meter Data Management (MDM)
Meter data repository
Usage history
Validation, estimation and editing
Customer billing data
Load Management (LM)
Load analysis
Load control
Demand response
Performance measurements
8
Risk management
© Copyright 2010 SISCO, Inc.
Information Model


The Static Information Model that contains the
metering classes, attributes and associations is
defined in detail in IEC61968 Part 11 or in IEC61970
Part 301.
Classes for Meter Reading and Control are contained
in the following Packages:
 Asset classes are defined in Asset package in 61968-11
 Customer classes are defined in the Customer package in
61968-11
 Metering classes are defined in the Metering package in
61968-11
 Prepayment classes are defined in the PaymentMetering
package in 61968
9
© Copyright 2010 SISCO, Inc.
Message Types

The key message payload structures include:
 CustomerMeterDataSet
 MeterAsset
 MeterAssetReading
 EndDeviceControls
 EndDeviceEvents
 MeterReadings
 MeterReadSchedule
 MeterServiceRequest
 MeterSystemEvents
 EndDeviceFirmware
10
© Copyright 2010 SISCO, Inc.
EndDeviceEvent Messages

EndDeviceEvent
Messages Convey
events related to:
 Sustained Outage
Detection
 Momentary Outage
Detection

Low Voltage Threshold
Detection

High Voltage
Threshold Detection
 Distortion Meter Health
 Tamper Detection
 Revenue Event
11
© Copyright 2010 SISCO, Inc.
EndDeviceAssets Message
12
© Copyright 2010 SISCO, Inc.
CustomerMeterDataSet Message
13
© Copyright 2010 SISCO, Inc.
MeterReadSchedule Message

Meter readings may be
requested using one or more
of the following parameters:
 Specific meter, using the
EndDeviceAsset mRID

Specific meter, using a
serialNumber as known to the
Metering System

EndDeviceGroups, where
an EndDeviceGroup identifies
a groupAddress used within
the Metering System

As specified using a
TimeSchedule

ReadingTypes can be
specified to identify the
desired reading types
14
© Copyright 2010 SISCO, Inc.
MeterReadings Message

MeterReadings message
allows for:
 Readings from one or
more meters
Reading values each
have an associated
reading type, timestamp
and value

Many Quality values can
be associated with each
reading value

Readings can be
supplied in the form of
interval blocks if the
common reading types are
grouped together.

Event Histories are
returned with meter
readings.
15
© Copyright 2010 SISCO, Inc.
MeterAssetReading Message



16
MeterAssetReading
messages may contain
many MeterService
Work items.
Each
MeterServiceWork item
identifies a MeterAsset
and Customer
There may be many
Readings and
EndDeviceEvents
obtained from the
MeterAsset.
© Copyright 2010 SISCO, Inc.
EndDeviceControls Message



17
Specific Meters may
be addresed by
CustomerAgreement,
EndDeviceAsset
and/or
EndDeviceGroup
At least one address
and a typeControl
attribute is required
for this message
TypeControl element
identifies the type of
control to be
performed
© Copyright 2010 SISCO, Inc.
MeterServiceRequests Message



18
May include one or
more
MeterServiceWork
items
Each item may refer
to a max of two
meters to provide a
means to replace a
meter.
Meter readings can
be obtained as a part
of the work.
© Copyright 2010 SISCO, Inc.
MeterSystemEvent Message


19
Supports the reporting
of activity within any
type of end device
(including meters), as
well as within the MS
communication
infrastructure
Can be used to
describe an event in the
end device itself, or in
the MS communication
infrastructure
© Copyright 2010 SISCO, Inc.
EndDeviceFirmware Message


20
Supports the naming of
the affected device
function, as well as
additional parameter
details that may be
necessary in the report
This structure, together
with the ActivityRecord
can effectively describe
the nature of the event,
when the event
occurred, and what has
happened
© Copyright 2010 SISCO, Inc.
ReceiptRecord Message


21
When MS receives
a payment, a receipt
is generated and the
relevant information
about the payment
is typically recorded
as a receipt record.
This information
may be accessed by
means of
ReceiptRecord
message payload.
© Copyright 2010 SISCO, Inc.
TransactionRecord Message

22
Information about
the sale of a prepaid
token or the receipt
of an account
payment is typically
recorded by MS in
the form a financial
transaction record
© Copyright 2010 SISCO, Inc.
SupplierConfig Message

23
Information about
the supplier (retailer
or utility for
example) of the
service may be
configured into MS
by means of
SupplierConfig
message payload
© Copyright 2010 SISCO, Inc.
Several Other Configuration Messages
24
CustomerConfig
Payload configures information about
customers of the supplier of the service
into the MS.
CustomerAgreementConfig
Payload configures information about
customer agreements into the MS.
CustomerAccountConfig
Payload configures information about
customer accounts into the MS.
AuxilaryAgreementConfig
Payload configures information about
customer debt for collection into the MS.
PricingStructureConfig
Payload configures information about
pricing structures into the MS.
© Copyright 2010 SISCO, Inc.
Several Other Configuration Messages - Continued
ServiceCategoryConfig
Payload configures information about the
categories of service (electricity, water,
gas for example) into the MS.
ServiceDeliveryPointConfig Payload configures information about the
service delivery points into the MS.
25
MeterAssetConfig
Payload configures information about the
meters in service into the MS.
SDPLocationConfig
Payload configures information about the
service delivery point locations into the
MS.
ServiceLocationConfig
Payload configures information about the
service locations into the MS.
© Copyright 2010 SISCO, Inc.
Questions & Contacts

Margaret Goodrich –
Home Office: 903-489-1494
Cell: 903-477-7176
Email: [email protected]
26
© Copyright 2010 SISCO, Inc.