Architectures for Interoperability Peter Egger & Dr Martin Gill - - PowerPoint PPT Presentation

▶
architectures for interoperability
SMART_READER_LITE
LIVE PREVIEW

Architectures for Interoperability Peter Egger & Dr Martin Gill - - PowerPoint PPT Presentation

Apr 29, 2023 33 likes •215 views

AEMC Briefing Architectures for Interoperability Peter Egger & Dr Martin Gill 31 st October 2013 AEMC Workshop Agenda 1. Possible Architectures as Interoperability moves through Not Interoperable Protocol Translation Common

slide-1
SLIDE 1

Architectures for Interoperability

Peter Egger & Dr Martin Gill 31st October 2013

AEMC Briefing

slide-2
SLIDE 2

Architectures for Interoperability v01

AEMC Workshop

  • 1. Possible Architectures as Interoperability moves through
  • Not Interoperable
  • Protocol Translation
  • Common Protocol
  • Interchangeable
  • 2. Examples
  • 3. Questions
  • 4. Appendix ‐ Interoperability Spectrum

2

Agenda

slide-3
SLIDE 3

Architectures for Interoperability v01

AEMC Workshop

The Power of Choice

3

What level of Interoperability and Access is required to support the aims of the Power of Choice (PoC)? Architectures (1)

Closed Direct Access Advanced Functions Metrology Functions Not Interoperable Interchangeable Common Protocol Protocol Translation

Interoperability Spectrum Access Spectrum

?

slide-4
SLIDE 4

Architectures for Interoperability v01

AEMC Workshop

Not Interoperable

4

Architectures (2)

Accredited Parties must develop a custom Application for each Smart Meter Operator with which they wish to communicate

slide-5
SLIDE 5

Architectures for Interoperability v01

AEMC Workshop

Protocol Translation – No Common Meter Protocol

5

Architectures (3)

Smart Meter Operator translates a common “market” protocol to the protocol supported by their meters

Meter Protocols are not interoperable

Accredited Parties must develop a custom Application supporting the common “market” protocol

Who defines the common “Market” protocol?

Smart Meter Operator free to choose their own meter protocol

Common Market Protocol

Assumes that the common market protocol is Australian Specific

slide-6
SLIDE 6

Architectures for Interoperability v01

AEMC Workshop

Protocol Translation – Common Meter Protocol

6

Architectures (4)

Development of the common market protocol is simplified by the common meter protocol

Smart Meter Operator translates a common “market” protocol to the common meter protocol Accredited Parties must develop a custom Application supporting the common “market” protocol

Two protocols

  • common meter protocol
  • common market protocol

Meter Protocols are interoperable

Smart Meter Operators are required to use a common meter protocol Assumes that the common market protocol is Australian Specific

Common Market Protocol

slide-7
SLIDE 7

Architectures for Interoperability v01

AEMC Workshop

Common Protocol – End‐to‐end Proprietary

7

Architectures (5)

All participants are limited to those vendors prepared to support the end‐to‐end proprietary protocol Accredited Parties likely to require a custom Application to implement the chosen end‐to‐end protocol

Meter Protocols are interoperable

Smart Meter Operators are required to use a common meter protocol

slide-8
SLIDE 8

Architectures for Interoperability v01

AEMC Workshop

Common Protocol – End‐to‐End Open & Non‐Proprietary

8

Architectures (6)

Standard solutions are available from a range of vendors

Meter Protocols are interoperable

Meter protocol supported by a range

  • f vendors

Standard Application

  • r may even be able

to use solutions hosted remotely

slide-9
SLIDE 9

Architectures for Interoperability v01

AEMC Workshop

Interchangeable

9

Architectures (7)

Interchangeable meters are either limited to the same communication technology or support a common hardware interface allowing different communications technologies to be plugged in (e.g. for geographic areas). Refer SMI FS Function 19 (Work‐in‐progress)

To make meters interchangeable there is a requirement to develop a comprehensive Companion Specification in addition to the end‐to‐end protocol

slide-10
SLIDE 10

Architectures for Interoperability v01

AEMC Workshop

10

Some Examples

slide-11
SLIDE 11

Architectures for Interoperability v01

AEMC Workshop

Victoria – Example of Protocol Translation

11

Examples (1)

After accepting the protocol the retailer must develop custom software to support the distributor’s protocol

The distributor has offered a protocol to retailers

slide-12
SLIDE 12

Architectures for Interoperability v01

AEMC Workshop

Victoria (cont)

12

Examples (2)

Without a market protocol Retailers may have to implement a different interface (protocol translation) for each distributor

While Victoria provides an example of protocol translation the lack

  • f a common market protocol results in the end‐to‐end interaction

falling between Not Interoperable and Protocol Translation

slide-13
SLIDE 13

Architectures for Interoperability v01

AEMC Workshop

New Zealand

13

Examples (3)

Without a common protocol each smart meter operator may have to implement a different interface (with protocol translation) for each retailer

In New Zealand the Smart Meter Operator must implement suitable protocols for the retailers.

slide-14
SLIDE 14

Architectures for Interoperability v01

AEMC Workshop

Protocol Translation ‐ Steps to add new functionality

14

Examples (4)

FRMP offers a customer a smart meter with New Functionality (“set a fixed daily budget”) SMO chooses meter vendor with a solution supporting new functionality. Restriction: must work with the selected SMCN FRMP and SMO negotiate changes to protocol to support new functionality. SMO contracts with the communications vendor to implement changes needed to support new functionality FRMP and SMO update their protocol translators to support the agreed protocol

All of these changes must be undertaken for EACH new function

slide-15
SLIDE 15

Architectures for Interoperability v01

AEMC Workshop

Common Protocol ‐ Adding new functionality

15

Examples (5)

SMO finds a meter vendor with a solution supporting new functionality. Restriction: Must support the Common Protocol FRMP offering the new functionality updates their back office FRMP offers a customer a smart meter with New Functionality (“set a fixed daily budget”)

slide-16
SLIDE 16

Architectures for Interoperability v01

AEMC Workshop

Questions

16

slide-17
SLIDE 17

Architectures for Interoperability v01

AEMC Workshop

17

Appendix

slide-18
SLIDE 18

Architectures for Interoperability v01

AEMC Workshop

Interoperability Spectrum

18

  • Not Interoperable
  • No ability to interact with the meter (e.g. Unpublished proprietary protocol)
  • Protocol Translation
  • Able to interact with the meter by converting protocols, however there may be some loss of functionality

e.g. Itron MV90 is only able to read meter data it cannot alter meter settings

  • Common Protocol
  • All meters use a common protocol so Accredited Parties are able to interact with all meters without loss of

functionality (may offer different functionality)

  • Interchangeable
  • One meter can be swapped with another with no system impacts. No need to change Head End Systems
  • r communications (also referred to as “Fully Interoperable”)

Not Interoperable Interchangeable Common Protocol Protocol Translation

Interoperability

From AEMC Terms of Reference: “The communication standard specifies the technical requirements of the communication network, in particular the form

  • f the commands sent to the meter and the information conveyed back from the meter.”

This is described as the meter protocol