SMP/B2B SLIDE 1 AGENDA Service types Communications mapping - - PowerPoint PPT Presentation

▶
smp b2b
SMART_READER_LITE
LIVE PREVIEW

SMP/B2B SLIDE 1 AGENDA Service types Communications mapping - - PowerPoint PPT Presentation

Dec 16, 2022 225 likes •397 views

SMP/B2B SLIDE 1 AGENDA Service types Communications mapping messaging and transactions Worked example #1 Worked example #2 Next steps SLIDE 2 SERVICE TYPES Infrastructure Services Advanced Meter Services On

slide-1
SLIDE 1

SLIDE 1

SMP/B2B

slide-2
SLIDE 2

SLIDE 2

AGENDA

  • Service types
  • Communications mapping – messaging and transactions
  • Worked example #1
  • Worked example #2
  • Next steps
slide-3
SLIDE 3

SLIDE 3

SERVICE TYPES

De-energisation

On Demand

Advanced Meter Services

Re-energisation (soft) Re-energisation (hard) Meter Read NMI Load Limit Load Management Meter Re-configuration NMI Enquiry Scheduled Read Provide Local Access to Metering System via Registered Device

Scheduled

New Connection Change Meter Test Meter Equipment Meter Fault Resolution Resolve Communication Failure Meter Investigation Revenue Assurance Investigation De-Energisation Re-Energisation NMI Supply Failure NMI Supply Restoration

Infrastructure Services

Meter Notifications

Supply Abolishment Combine & Centralise NMIs Verify Standing Data

Connection Services Information Services

Provide Meter Data Verify Meter Data Notice of Works

Notifications

Meter Replacement Required Planned Interruption Notification of NMI Connection Status

slide-4
SLIDE 4

SLIDE 4

COMMUNICATIONS MAPPING

  • The SMP/B2B is a system for the communication of

service requests.

  • While there are many service types, the details of the

communications are simply “payloads” within a much smaller potential range of types of SMP/B2B interactions.

  • “Communications Mapping” is about the relative few

different ways the SMP/B2B could be used to communicate without requiring us to focus on the detail

  • f the payloads that describe the service request.
slide-5
SLIDE 5

SLIDE 5

MESSAGING VS A TRANSACTION

  • Messaging
  • One party sends a communication to another, which could be a

notification or a request for action

  • If a response to a message is required, the respondent sends a

communication to the requesting party

  • The current B2B e-hub is designed to support messaging
  • All workflow is managed outside the B2B e-hub
  • Transaction
  • The sender provides a notification, or service request to a system
  • The system then sends on a notification or request to one or more

parties and tracks and directs responses back to the appropriate party (based on a pre-defined set of rules)

  • Facilitates the automation of one or more messages between one or

more parties

  • Communication workflow can be managed within the B2B e-hub
  • Could potentially include auto-update of MSATS
slide-6
SLIDE 6

SLIDE 6

COMMUNICATIONS MAPPING

  • 1. Notifications - sender to receiver (no response)
  • 2. Request for action - sender to receiver, with response

from receiver to sender.

  • 3. Request for action with notification of secondary

party – sender to receiver, with notification of request to third party, and response from receiver to sender.

Sender Receiver Sender Receiver Sender Receiver 3rd Party Receiver 3rd Party Sender OR

slide-7
SLIDE 7

SLIDE 7

COMMUNICATIONS MAPPING

  • 4. Request for action to multiple parties – sender to

more than one receiver (e.g. up to 2), with each receiver responding to the sender.

  • 5. Request for action with notification of completion to

secondary party - sender to receiver, sending response to sender and notification of completion to third party.

OR Receiver 2 Receiver 1 Sender Sender Receiver 2 Receiver 1 Sender Receiver 3rd Party OR 3rd Party Sender Receiver

slide-8
SLIDE 8

SLIDE 8

COMMUNICATIONS MAPPING

6. Request for action where 3rd party is notified on request and completion – sender to receiver with notification to third party, with receiver sending response to sender and notification of completion to third party.

OR 3rd Party Sender Receiver Sender Receiver 3rd Party

slide-9
SLIDE 9

SLIDE 9

WORKED EXAMPLE #1 SUPPLY ABOLISHMENT

slide-10
SLIDE 10

SLIDE 10

WORKED EXAMPLE 1 SUPPLY ABOLISHMENT

Retailer Distributor

  • 1. Where Distributor is the Service Provider

2.Where Distributor is not the Service Provider 2A Retailer Distributor Distributor OR Retailer Service Provider Service Provider

slide-11
SLIDE 11

SLIDE 11

WORKED EXAMPLE 2 SUPPLY ABOLISHMENT

2.Where Distributor is not the Service Provider OR Distributor Retailer Retailer Distributor 2B Service Provider Service Provider

Intention of the diagram - Service Provider notified by Distributor on completion

OR Distributor Retailer Distributor 2C Service Provider Service Provider Retailer

slide-12
SLIDE 12

SLIDE 12

WORKED EXAMPLE #2 CHANGE METER

slide-13
SLIDE 13

SLIDE 13

WORKED EXAMPLE 2 CHANGE METER

Retailer Distributor

  • 1. Where Distributor is the Service Provider

Distributor cannot be Service Provider for Advanced Metering

slide-14
SLIDE 14

SLIDE 14

WORKED EXAMPLE 1 CHANGE METER

2.Where Distributor is not the Service Provider 2B Retailer Distributor Distributor OR Retailer Service Provider Service Provider 2A OR Distributor Retailer Retailer Distributor Service Provider Service Provider

slide-15
SLIDE 15

SLIDE 15

NEXT STEPS

  • AEMO to develop strawman comms mapping across all

service types

  • Transitional IEC group:
  • Notifications have been sent regarding the establishment
  • f the transitional group in preparation for the new IEC
  • The immediate focus is to establish the group
  • Once established, we will be presenting the material

developed to date and seeking guidance on next steps from the group

  • Next meeting TBC