smp b2b
play

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

Dec 16, 2022 •225 likes •394 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

  1. SMP/B2B SLIDE 1

  2. AGENDA • Service types • Communications mapping – messaging and transactions • Worked example #1 • Worked example #2 • Next steps SLIDE 2

  3. SERVICE TYPES Infrastructure Services Advanced Meter Services On Demand Scheduled Connection Services Information Services De-energisation Scheduled Read New Connection Verify Standing Data Re-energisation (soft) Change Meter Provide Meter Data Verify Meter Data Re-energisation (hard) Meter Notifications Test Meter Equipment Meter Read Meter Fault Resolution Notifications NMI Supply Failure Resolve Communication NMI Load Limit Failure NMI Supply Restoration Load Management Meter Investigation Notice of Works Revenue Assurance Meter Re-configuration Meter Replacement Investigation Required NMI Enquiry De-Energisation Planned Interruption Provide Local Access to Notification of NMI Re-Energisation Metering System via Connection Status Registered Device Supply Abolishment Combine & Centralise NMIs SLIDE 3

  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 of the payloads that describe the service request. SLIDE 4

  5. MESSAGING VS A TRANSACTION • Messaging o One party sends a communication to another, which could be a notification or a request for action o If a response to a message is required, the respondent sends a communication to the requesting party o The current B2B e-hub is designed to support messaging o All workflow is managed outside the B2B e-hub • Transaction o The sender provides a notification, or service request to a system o 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) o Facilitates the automation of one or more messages between one or more parties o Communication workflow can be managed within the B2B e-hub o Could potentially include auto-update of MSATS SLIDE 5

  6. COMMUNICATIONS MAPPING 1. Notifications - sender to receiver (no response) Sender Receiver 2. Request for action - sender to receiver, with response from receiver to sender. Sender Receiver 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. 3 rd Party 3 rd Party OR Sender Receiver Sender Receiver SLIDE 6

  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. Receiver 1 Receiver 1 OR Sender Receiver 2 Sender Receiver 2 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. Sender Receiver Sender Receiver OR 3 rd Party 3 rd Party SLIDE 7

  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. 3 rd Party 3 rd Party OR Sender Receiver Sender Receiver SLIDE 8

  9. WORKED EXAMPLE #1 SUPPLY ABOLISHMENT SLIDE 9

  10. WORKED EXAMPLE 1 SUPPLY ABOLISHMENT 1. Where Distributor is the Service Provider Retailer Distributor 2.Where Distributor is not the Service Provider Service Service Provider Provider OR 2A Retailer Distributor Distributor Retailer SLIDE 10

  11. WORKED EXAMPLE 2 SUPPLY ABOLISHMENT 2.Where Distributor is not the Service Provider Service Service Provider Provider OR 2B Distributor Distributor Retailer Retailer Intention of the diagram - Service Provider notified by Distributor on completion Service Service Provider Provider OR 2C Distributor Distributor Retailer Retailer SLIDE 11

  12. WORKED EXAMPLE #2 CHANGE METER SLIDE 12

  13. WORKED EXAMPLE 2 CHANGE METER 1. Where Distributor is the Service Provider  Retailer Distributor Distributor cannot be Service Provider for Advanced Metering SLIDE 13

  14. WORKED EXAMPLE 1 CHANGE METER 2.Where Distributor is not the Service Provider Distributor Distributor 2A OR Service Service Retailer Retailer Provider Provider Distributor Distributor OR 2B Retailer Service Service Retailer Provider Provider SLIDE 14

  15. NEXT STEPS • AEMO to develop strawman comms mapping across all service types • Transitional IEC group: o Notifications have been sent regarding the establishment of the transitional group in preparation for the new IEC o The immediate focus is to establish the group o Once established, we will be presenting the material developed to date and seeking guidance on next steps from the group • Next meeting TBC SLIDE 15

Recommend

More recommend