74
Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations Utility Reference Model 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) April 2013

Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

  • Upload
    others

  • View
    2

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations Utility Reference Model5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

April 2013

Page 2: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Oracle Utilities SGG V2.0.0 to MDM V2.0.1 Integration Utility Reference Model 5.6.3.4b

Copyright © 2012, 2013, Oracle and/or its affiliates. All rights reserved.

This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd. 0611

Page 3: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

ContentsContentsChapter 1Overview............................................................................................................................................................. 1-1

Brief Description ............................................................................................................................................................ 1-2

Chapter 2Detailed Business Process Model Description ................................................................................................ 2-1

Business Process Diagrams........................................................................................................................................... 2-2Manage Device Remote Connect (Echelon) Page 1................................................................................. 2-2Manage Device Remote Connect (Echelon) Page 2................................................................................. 2-3Manage Device Remote Connect (Echelon) Page 3................................................................................. 2-5Manage Device Remote Connect (Echelon) Page 4................................................................................. 2-6Manage Device Remote Connect (Echelon) Page 5................................................................................. 2-7Manage Device Remote Connect (Echelon) Page 6................................................................................. 2-9Manage Device Remote Connect (Echelon) Page 7............................................................................... 2-10Manage Device Remote Connect (Echelon) Page 8............................................................................... 2-11Manage Device Remote Connect (Echelon) Page 9............................................................................... 2-12Manage Device Remote Connect (Echelon) Page 10 ............................................................................ 2-13

Manage Device Remote Connect (Echelon) Description...................................................................................... 2-141.0 Gather Requirements to Create Command....................................................................................... 2-171.1 Select Command Activity Type........................................................................................................... 2-181.2 Select Device and Populate Command Execution Data ................................................................. 2-181.3 Submit Request ...................................................................................................................................... 2-181.4 Communicate and Transform Remote Connect Command to SGG Format ............................. 2-181.5 Add to JMS Queue ................................................................................................................................ 2-181.6 Call Web service..................................................................................................................................... 2-191.7 Identify Device and Head-End (Service Provider) .......................................................................... 2-191.8 Determine if Device is Smart Device................................................................................................. 2-191.9 Determine Method to Create Remote Connect Activity................................................................. 2-202.0 Determine Send Method and Send Error Message.......................................................................... 2-202.1 Communicate and Transform Message ............................................................................................. 2-202.2 Receive and Process Message .............................................................................................................. 2-212.3 Determine Activity Type ...................................................................................................................... 2-212.4 Validate Required Data......................................................................................................................... 2-212.5 Create Remote Connect Activity in Pending State........................................................................... 2-222.6 Validate Ability to Process Command and Transition Activity to Validate State ....................... 2-222.7 Transition Activity to Validation Error State and Log Error ......................................................... 2-232.8 Create To Do ......................................................................................................................................... 2-232.9 Send Response "Command Received" and Transition to Wait for Eff. Date State ................... 2-243.0 Evaluate Availability of Command Execution Date and Time...................................................... 2-243.1 Review Activity in Eff. Date State ...................................................................................................... 2-253.2 Request to Delete Activity ................................................................................................................... 2-253.3 Delete Activity........................................................................................................................................ 2-253.4 Request to Discard Activity ................................................................................................................. 2-26

i

Page 4: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

ii

3.5 Populate Changes and Request to Update......................................................................................... 2-263.6 Update Activity ...................................................................................................................................... 2-263.7 Request to Connect Device ................................................................................................................. 2-263.8 Transition Activity to Connection Ready State ................................................................................ 2-273.9 5.6.3.6b SGG-MDM.Manage Device Device Status Check (Echelon)......................................... 2-274.0 Transition Activity to Connection Ready State ................................................................................ 2-284.0.1 Evaluate Request if Meter Read is Required .................................................................................. 2-284.1 5.6.3.1b SGG-MDM.Manage On-Demand Read (Echelon).......................................................... 2-284.2 Transition Activity to Connection Ready State ................................................................................ 2-284.3 Transition Activity to Communication in Progress State................................................................ 2-294.4 Evaluate Wait Period for Response.................................................................................................... 2-294.5 Transition Activity to Communication Error State and Log Error............................................... 2-294.6 Review Activity in Comm. In Progress State .................................................................................... 2-304.7 Request to Retry Activity...................................................................................................................... 2-304.8 Transition Activity to Retry State........................................................................................................ 2-304.9 Cancel Outstanding Outbound Communication ............................................................................. 2-305.0 Initiate Remote Connect Outbound Communication..................................................................... 2-315.1 Create Outbound Communication in Pending State ....................................................................... 2-315.2 Validate Ability to Process Outbound Communication and Transition to Validate State ........ 2-325.3 Transition Outbound Communication to Validation Error State and Log Error ...................... 2-325.4 Populate Connect Request Details and Transition to Awaiting Response State ......................... 2-325.5 Create and Send Outbound Communication Message to Echelon Head-End System ............. 2-335.6 Communicate and Transform Message to Echelon Format .......................................................... 2-335.7 Receive and Process Request Message............................................................................................... 2-335.8 Receive and Process Device Connect Request ................................................................................. 2-345.9 Analyze Message and Send Acknowledgement ................................................................................ 2-346.0 Communicate and Transform Acknowledgement to SGG Format.............................................. 2-346.1 Evaluate Acknowledgement ................................................................................................................ 2-346.2 Log Error and Transition to Response Error State ......................................................................... 2-346.3 Evaluate Wait Period for Response.................................................................................................... 2-356.4 Log Error and Transition to Response Error State ......................................................................... 2-356.5 Review Outbound Communication.................................................................................................... 2-366.6 Request to Discard ................................................................................................................................ 2-366.7 Transition Outbound Communication to Discard State................................................................. 2-366.8 Populate Changes and Request to Update......................................................................................... 2-366.9 Update Outbound Communication.................................................................................................... 2-377.0 Request to Retry .................................................................................................................................... 2-377.1 Transition Outbound Communication to Retry State ..................................................................... 2-377.2 Send Remote Connect Response to Echelon Head End System .................................................. 2-387.3 Receive and Process Remote Connect Response to Echelon SGG.............................................. 2-387.4 Communicate and Transform Remote Connect Response to Echelon SGG Format............... 2-387.4.1 Identify Response Message and Processing Method .................................................................... 2-387.5 Pre-process Inbound Message............................................................................................................. 2-397.6 Create Inbound Communication in Pending State .......................................................................... 2-397.7 Validate Ability to Process Inbound Communication and Transition to Validate State............ 2-407.8 Transition Inbound Communication to Validation Error State and Log Error.......................... 2-407.9 Transition to Create Completion Event State................................................................................... 2-418.0 Validate and Create Device Connect Completion Event in Pending State.................................. 2-418.1 Transition Inbound to Completed State ............................................................................................ 2-418.2 Transition Outbound Communication to Completed State ........................................................... 2-428.3 Transition Activity to Execution Completion Event State ............................................................. 2-428.4 Transition Meter Read Completion Event to Executed State........................................................ 2-428.5 Preprocess IMD..................................................................................................................................... 2-438.6 Transition Device Connect Completion Event to Executed State................................................ 2-438.7 Update Device Install Event to 'Connect' State ............................................................................... 2-43

Page 5: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

8.8 Transition Activity to Completion Event Error State and Log Error .......................................... 2-448.9 Transition Activity to Waiting for Measurement State.................................................................... 2-449.1 4.2.1.2 MDM.Manage VEE and VEE Exceptions .......................................................................... 2-449.2 Retrieve and Store Final Measurements............................................................................................. 2-449.3 Retrieve and Store Initial Measurements ........................................................................................... 2-459.4 Monitor IMD Availability within Allowable Period......................................................................... 2-459.5 Transition Activity to Wait Expired Error State and Log Error.................................................... 2-469.6 Review Activity Waiting for Measurement........................................................................................ 2-469.7 Request to Complete............................................................................................................................. 2-469.8 Transition Activity to Completion State ............................................................................................ 2-479.9 Create and Send Connect Success Notification to Requester ........................................................ 2-4710.0 Create and Send Meter Read to Requester ...................................................................................... 2-4710.1 Transition Activity to Discard State ................................................................................................. 2-4810.2 Cancel Outstanding Completion Events ......................................................................................... 2-4810.3 Send Response “Command Failed” to Requester.......................................................................... 2-4810.4 Analyze Requirements to Create Event ........................................................................................... 2-4810.5 Select Completion Event Type and Populate Data ....................................................................... 2-4910.6 Request to Create Completion Event .............................................................................................. 2-4910.7 Review Event ....................................................................................................................................... 2-4910.8 Request to Delete Event .................................................................................................................... 2-4910.9 Delete Completion Event .................................................................................................................. 2-5011.0 Request to Discard Event .................................................................................................................. 2-5011.1 Transition to Discard State and Discard Completion Event........................................................ 2-5011.2 Request to Update Event ................................................................................................................... 2-5111.3 Update Completion Event ................................................................................................................. 2-5111.4 Request to Execute ............................................................................................................................. 2-5111.5 Gather Requirements to Cancel Command .................................................................................... 2-5111.6 Select Cancel Command Activity Type............................................................................................ 2-5211.7 Populate Cancel Command Execution Data .................................................................................. 2-5211.8 Communicate and Transform Remote Connect Cancel Command to SGG Format.............. 2-5211.9 Identify Remote Connect Activity based on Transaction ID....................................................... 2-5212.0 Analyze Error and Work To Do....................................................................................................... 2-5212.1 Request to Delete ................................................................................................................................ 2-5312.2 Delete Inbound Communication...................................................................................................... 2-5312.3 Request to Discard .............................................................................................................................. 2-5312.4 Complete To Do(s) ............................................................................................................................. 2-5412.5 Transition Inbound Communication to Discard State.................................................................. 2-5412.6 Log Error and Transition Outbound Communication to Response Error State...................... 2-5412.7 Request to Validate ............................................................................................................................. 2-5412.8 Transition to Validate State and Initialize Reprocessing ............................................................... 2-5512.9 Identify Inbound Communication in Validation Error State ....................................................... 2-5513.0 Evaluate Criteria to Run Automated Retry Process....................................................................... 2-5513.1 Request to Delete ................................................................................................................................ 2-5613.2 Delete Outbound Communication................................................................................................... 2-5613.3 Request to Validate ............................................................................................................................. 2-5613.4 Transition to Validate State and Initialize Reprocessing ............................................................... 2-5713.5 Identify Outbound Communication in Validation Error State.................................................... 2-5713.6 Transition Outbound Communication to Retry State................................................................... 2-5713.7 Identify Outbound Communication in Response Error State ..................................................... 2-5813.8 Request to Revalidate.......................................................................................................................... 2-5813.9 Transition Activity to Validate State and Initialize Reprocessing ................................................ 2-5814.0 Identify Activity in Validation Error State ...................................................................................... 2-5914.1 Transition Activity to Retry State...................................................................................................... 2-5914.2 Identify Activity in Communication Error State ............................................................................ 2-5914.3 Request to Execute Completion Event ........................................................................................... 2-60

iii

Page 6: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

iv

14.4 Transition Activity to Execution Completion Event State and Initialize Reprocessing .......... 2-6014.5 Identify Activity in Completion Event Error State........................................................................ 2-6014.6 Request to Continue Waiting............................................................................................................. 2-6114.7 Transition Activity to Waiting for Measurement State and Initialize Reprocessing ................. 2-6114.8 Identify Activity in Wait Expired Error State ................................................................................. 2-61

Business Objects Lifecycle......................................................................................................................................... 2-63D1-RemoteConnect..................................................................................................................................... 2-63D4-ConnectLoad ......................................................................................................................................... 2-64D4-ConnectLoadNtf ................................................................................................................................... 2-65D1-Completion Event ................................................................................................................................ 2-66

Page 7: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Chapter 1Overview

This chapter provides a brief description of the SGG-MDM.Manage Device Remote Connect (Echelon) business process and associated process diagrams. This includes:

• Brief Description

Overview 1-1

Page 8: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Brief Description

Brief DescriptionBusiness Process: 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Process Type: Process

Parent Process: 5.6.3 SGG-MDM.Manage Devices

Sibling Processes: 5.6.3.1b SGG-MDM.Manage On-Demand Read (Echelon), 5.6.3.6b SGG-MDM.Manage Device Device Status Check (Echelon)

This process gets initiated when a 3rd Party application (E.g. Customer Care and Billing application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device Remote Connect within SGG system. SGG initiates Remote Connect by communicating with respective Echelon Head-End System that in turn communicates with the Smart Meter device, for device connection, and sends response back to SGG. Head-End System also checks load status and collects meter read from Smart Meter device, if required, as part of Device Remote Connect process.

1-2 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 9: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Chapter 2Detailed Business Process Model Description

This chapter provides a detailed description of the SGG-MDM.Manage Device Remote Connect (Echelon) business process. This includes:

• Business Process Diagrams

• Manage Device Remote Connect (Echelon) Page 1

• Manage Device Remote Connect (Echelon) Page 2

• Manage Device Remote Connect (Echelon) Page 3

• Manage Device Remote Connect (Echelon) Page 4

• Manage Device Remote Connect (Echelon) Page 5

• Manage Device Remote Connect (Echelon) Page 6

• Manage Device Remote Connect (Echelon) Page 7

• Manage Device Remote Connect (Echelon) Page 8

• Manage Device Remote Connect (Echelon) Page 9

• Manage Device Remote Connect (Echelon) Page 10

• Manage Device Remote Connect (Echelon) Description

• Business Objects Lifecycle

• D1-RemoteConnect

• D4-ConnectLoad

• D4-ConnectLoadNtf

• D1-Completion Event

Detailed Business Process Model Description 2-1

Page 10: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

iness Process Model Description 2-2

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Bus

Business Process Diagrams

Manage Device Remote Connect (Echelon) Page 1

Page 11: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

iness Process Model Description 2-3

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Bus

Manage Device Remote Connect (Echelon) Page 2

Page 12: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

iness Process Model Description 2-4

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Bus
Page 13: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

iness Process Model Description 2-5

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Bus

Manage Device Remote Connect (Echelon) Page 3

Page 14: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

iness Process Model Description 2-6

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Bus

Manage Device Remote Connect (Echelon) Page 4

Page 15: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

iness Process Model Description 2-7

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Bus

Manage Device Remote Connect (Echelon) Page 5

Page 16: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

iness Process Model Description 2-8

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Bus
Page 17: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

iness Process Model Description 2-9

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Bus

Manage Device Remote Connect (Echelon) Page 6

Page 18: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

ess Process Model Description 2-10

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Busin

Manage Device Remote Connect (Echelon) Page 7

Page 19: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

ess Process Model Description 2-11

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Busin

Manage Device Remote Connect (Echelon) Page 8

Page 20: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

ess Process Model Description 2-12

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Busin

Manage Device Remote Connect (Echelon) Page 9

Page 21: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Process Diagrams

ess Process Model Description 2-13

5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon) Detailed Busin

Manage Device Remote Connect (Echelon) Page 10

Page 22: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Manage Device Remote Connect (Echelon) DescriptionThis section includes detailed descriptions of the steps involved in the SGG-MDM.Manage Device Remote Connect (Echelon) business process, including:

• 1.0 Gather Requirements to Create Command

• 1.1 Select Command Activity Type

• 1.2 Select Device and Populate Command Execution Data

• 1.3 Submit Request

• 1.4 Communicate and Transform Remote Connect Command to SGG Format

• 1.5 Add to JMS Queue

• 1.6 Call Web service

• 1.7 Identify Device and Head-End (Service Provider)

• 1.8 Determine if Device is Smart Device

• 1.9 Determine Method to Create Remote Connect Activity

• 2.0 Determine Send Method and Send Error Message

• 2.1 Communicate and Transform Message

• 2.2 Receive and Process Message

• 2.3 Determine Activity Type

• 2.4 Validate Required Data

• 2.5 Create Remote Connect Activity in Pending State

• 2.6 Validate Ability to Process Command and Transition Activity to Validate State

• 2.7 Transition Activity to Validation Error State and Log Error

• 2.9 Send Response "Command Received" and Transition to Wait for Eff. Date State

• 3.0 Evaluate Availability of Command Execution Date and Time

• 3.1 Review Activity in Eff. Date State

• 3.2 Request to Delete Activity

• 3.3 Delete Activity

• 3.4 Request to Discard Activity

• 3.5 Populate Changes and Request to Update

• 3.6 Update Activity

• 3.7 Request to Connect Device

• 3.8 Transition Activity to Connection Ready State

• 3.9 5.6.3.6b SGG-MDM.Manage Device Device Status Check (Echelon)

• 4.0 Transition Activity to Connection Ready State

• 4.0.1 Evaluate Request if Meter Read is Required

• 4.1 5.6.3.1b SGG-MDM.Manage On-Demand Read (Echelon)

• 4.2 Transition Activity to Connection Ready State

• 4.3 Transition Activity to Communication in Progress State

2-14 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 23: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

• 4.4 Evaluate Wait Period for Response

• 4.4 Evaluate Wait Period for Response

• 4.5 Transition Activity to Communication Error State and Log Error

• 4.6 Review Activity in Comm. In Progress State

• 4.7 Request to Retry Activity

• 4.8 Transition Activity to Retry State

• 4.9 Cancel Outstanding Outbound Communication

• 5.0 Initiate Remote Connect Outbound Communication

• 5.1 Create Outbound Communication in Pending State

• 5.2 Validate Ability to Process Outbound Communication and Transition to Validate State

• 5.3 Transition Outbound Communication to Validation Error State and Log Error

• 5.4 Populate Connect Request Details and Transition to Awaiting Response State

• 5.5 Create and Send Outbound Communication Message to Echelon Head-End System

• 5.6 Communicate and Transform Message to Echelon Format

• 5.7 Receive and Process Request Message

• 5.8 Receive and Process Device Connect Request

• 5.9 Analyze Message and Send Acknowledgement

• 6.0 Communicate and Transform Acknowledgement to SGG Format

• 6.1 Evaluate Acknowledgement

• 6.2 Log Error and Transition to Response Error State

• 6.3 Evaluate Wait Period for Response

• 6.4 Log Error and Transition to Response Error State

• 6.5 Review Outbound Communication

• 6.6 Request to Discard

• 6.7 Transition Outbound Communication to Discard State

• 6.8 Populate Changes and Request to Update

• 6.9 Update Outbound Communication

• 7.0 Request to Retry

• 7.1 Transition Outbound Communication to Retry State

• 7.2 Send Remote Connect Response to Echelon Head End System

• 7.3 Receive and Process Remote Connect Response to Echelon SGG

• 7.4.1 Identify Response Message and Processing Method

• 7.5 Pre-process Inbound Message

• 7.6 Create Inbound Communication in Pending State

• 7.7 Validate Ability to Process Inbound Communication and Transition to Validate State

• 7.8 Transition Inbound Communication to Validation Error State and Log Error

Detailed Business Process Model Description 2-15

Page 24: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

• 7.9 Transition to Create Completion Event State

• 8.0 Validate and Create Device Connect Completion Event in Pending State

• 8.1 Transition Inbound to Completed State

• 8.2 Transition Outbound Communication to Completed State

• 8.3 Transition Activity to Execution Completion Event State

• 8.4 Transition Meter Read Completion Event to Executed State

• 8.5 Preprocess IMD

• 8.6 Transition Device Connect Completion Event to Executed State

• 8.7 Update Device Install Event to 'Connect' State

• 8.8 Transition Activity to Completion Event Error State and Log Error

• 8.9 Transition Activity to Waiting for Measurement State

• 9.1 4.2.1.2 MDM.Manage VEE and VEE Exceptions

• 9.2 Retrieve and Store Final Measurements

• 9.3 Retrieve and Store Initial Measurements

• 9.4 Monitor IMD Availability within Allowable Period

• 9.5 Transition Activity to Wait Expired Error State and Log Error

• 9.6 Review Activity Waiting for Measurement

• 9.7 Request to Complete

• 9.8 Transition Activity to Completion State

• 9.9 Create and Send Connect Success Notification to Requester

• 10.0 Create and Send Meter Read to Requester

• 10.1 Transition Activity to Discard State

• 10.2 Cancel Outstanding Completion Events

• 10.3 Send Response “Command Failed” to Requester

• 10.4 Analyze Requirements to Create Event

• 10.5 Select Completion Event Type and Populate Data

• 10.6 Request to Create Completion Event

• 10.7 Review Event

• 10.8 Request to Delete Event

• 10.9 Delete Completion Event

• 11.0 Request to Discard Event

• 11.1 Transition to Discard State and Discard Completion Event

• 11.2 Request to Update Event

• 11.3 Update Completion Event

• 11.4 Request to Execute

• 11.5 Gather Requirements to Cancel Command

• 11.6 Select Cancel Command Activity Type

• 11.7 Populate Cancel Command Execution Data

2-16 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 25: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

• 11.8 Communicate and Transform Remote Connect Cancel Command to SGG Format

• 11.9 Identify Remote Connect Activity based on Transaction ID

• 12.0 Analyze Error and Work To Do

• 12.1 Request to Delete

• 12.2 Delete Inbound Communication

• 12.3 Request to Discard

• 12.4 Complete To Do(s)

• 12.5 Transition Inbound Communication to Discard State

• 12.6 Log Error and Transition Outbound Communication to Response Error State

• 12.7 Request to Validate

• 12.8 Transition to Validate State and Initialize Reprocessing

• 12.9 Identify Inbound Communication in Validation Error State

• 13.0 Evaluate Criteria to Run Automated Retry Process

• 13.1 Request to Delete

• 13.2 Delete Outbound Communication

• 13.3 Request to Validate

• 13.4 Transition to Validate State and Initialize Reprocessing

• 13.5 Identify Outbound Communication in Validation Error State

• 13.6 Transition Outbound Communication to Retry State

• 13.7 Identify Outbound Communication in Response Error State

• 13.8 Request to Revalidate

• 13.9 Transition Activity to Validate State and Initialize Reprocessing

• 14.0 Identify Activity in Validation Error State

• 14.1 Transition Activity to Retry State

• 14.2 Identify Activity in Communication Error State

• 14.3 Request to Execute Completion Event

• 14.4 Transition Activity to Execution Completion Event State and Initialize Reprocessing

• 14.5 Identify Activity in Completion Event Error State

• 14.6 Request to Continue Waiting

• 14.7 Transition Activity to Waiting for Measurement State and Initialize Reprocessing

• 14.8 Identify Activity in Wait Expired Error State

1.0 Gather Requirements to Create CommandSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Detailed Business Process Model Description 2-17

Page 26: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Description: MDM or SGG Authorized User analyzes requirements and gathers information required to create Remote Connect command.

1.1 Select Command Activity TypeSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User selects Activity Type to create a Remote Connect command request.

1.2 Select Device and Populate Command Execution DataSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User selects the device and populates required data such as request effective date, request expiration date, etc. User also indicates if the command is optional, if future disconnect command is present, and can even indicate if start measurement is to be retrieved as part of connect process.

1.3 Submit RequestSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User submits request using manual request screen.

1.4 Communicate and Transform Remote Connect Command to SGG FormatSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: Integration Layer

Description: Integration Layer facilitates the communication between the 3rd Party application and the SGG application. It receives the Remote Connect request, transforms, and converts the request into format compatible with SGG Application.

1.5 Add to JMS QueueSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Entities to Configure

Activity Type

Business Object(s)

D1-RemoteConnect

2-18 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 27: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Actor/Role: Integration Layer

Description: Integration Layer adds the Remote Connect request to JMS queue.

1.6 Call Web serviceSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: Integration Layer

Description: Integration Layer calls web services to process further the Remote Connect request.

1.7 Identify Device and Head-End (Service Provider)See Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Group: Generic Device Connect Processing

Actor/Role: SGG

Description: SGG initiates pre-processing of the Remote Connect request that came from 3rd Party Application. It attempts to read the request message and determines the Device for which the connect request is made, and the Head-End system that communicates with the device.

1.8 Determine if Device is Smart DeviceSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Group: Generic Device Connect Processing

Actor/Role: SGG

Description: The application determines whether the request for Remote Connect is for Smart Device or not.

Note: Currently application processes requests for Smart Devices only. Service Requests functionality will be included in later releases.

Entities to Configure

Device

Head -End System (Service Provider)

Business Objects Available Algorithms

D1-GenericConnect D1-DDR (Determine Device and Recipient)

Entities to Configure

Device

Device Configuration

Detailed Business Process Model Description 2-19

Page 28: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

1.9 Determine Method to Create Remote Connect ActivitySee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Group: Generic Device Connect Processing

Actor/Role: SGG

Description: SGG determines the method to create Activity if the device is found to be a Smart Device.

2.0 Determine Send Method and Send Error MessageSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG determines the method to send the error message to 3rd Party application and sends it.

Note: Sending mechanism could be different and depends on application landscape. Currently it is determined based on customer requirements.

2.1 Communicate and Transform MessageSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: Integration Layer

Description: Integration Layer receives the outbound message from SGG, transforms, and converts it into format compatible with 3rd Party Application.

Business Objects Available Algorithms

D1-GenericConnect D1-CDCCSRTBO ( Transform to Connect Command Request or Connect Service Request Transaction BO)

Entities to Configure

Device Configuration

Service Provider

Business Objects Available Algorithms

D1-GenericConnect D1-CDCCSRTBO (Transform to Connect Command Request or Connect Service Request Transaction BO)

2-20 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 29: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

2.2 Receive and Process Message See Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: 3rd Party application

Description: 3rd Party Application receives message from SGG and processes it.

2.3 Determine Activity TypeSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Group: Pre-process Activity

Actor/Role: SGG

Description: SGG identifies the Activity Type to be assigned to the Activity to be created.

Note: Typically system has different Activity types configured to reflect different business scenarios, and currently the system will select the Activity type related to Connect command action.

2.4 Validate Required DataSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Group: Pre-process Activity

Actor/Role: SGG

Description: SGG validates the availability and correctness of required information. Usually, system checks for Requester information, Device information, Effective Date/Time and Expiration Date/Time, etc.

Entities to Configure

Activity Type

To Do Type

To Do Role

Business Objects Available Algorithms

D1-RemoteConnect D1-DETACTTYP (Determine Activity Type)

Entities to Configure

Device

Edge Application Details

Detailed Business Process Model Description 2-21

Page 30: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

2.5 Create Remote Connect Activity in Pending StateSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG creates Remote Connect Activity in 'Pending' state.

2.6 Validate Ability to Process Command and Transition Activity to Validate State

See Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Group: Validate Ability to Process Command

Actor/Role: SGG

Description: SGG validates ability to process Remote Connect request. Typically, system validates current Device connection status, Presence of at least one Scalar MC, Ability of Head-End to support On-demand Read, Ability of Head-End to perform Connect, and also checks if already any Connect command or Disconnect command is issued, etc.

Business Objects Available Algorithms

D1-RemoteConnect D1-GINPVAL (Common Input Validation)D1-VALMDEST (Validate Measurement Destination)D1-VALMREQO (Validate Measurement Requested)D1-MFRSMVAL (Measurement Fields for Retrieve Start Measurement Validation)

Business Objects

D1-RemoteConnect

D1-RemoteConnectType

Entities to Configure

Device

Measuring Components

Processing Method for On-Demand Read

Processing Method for Connect

2-22 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 31: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

2.7 Transition Activity to Validation Error State and Log ErrorSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Group: Validate Ability to Process Command

Actor/Role: SGG

Description: If any error occurs during validations, SGG transitions the Activity to 'Validation Error' state and logs an error.

2.8 Create To DoSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: Once an error is logged, SGG creates a 'To Do' entry for the Authorized User.

Business Objects Available Algorithms

D1-RemoteConnect D1-VALACTTDI (Validate Activity Type and Transition to Error State if Invalid)D1-VALDVCNCD (Validate Device is not already Connected)D1-VALDEVMCS (Validate that Device has appropriate Measuring Component)D1-VHCPODR (Validate Head-End's Capability to perform On-Demand Read)D1-VHCPCD (Validate Head-End's Capability to perform Connect DisconnectD1-CACTCONN (Check for Existing Active Connect Command Request)D1-CHKDISCON (Check for Concurrent Disconnect Command Request)F1-AT-RQJ (Transition to Default Next Status)

Business Object

D1-RemoteConnect

Detailed Business Process Model Description 2-23

Page 32: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

2.9 Send Response "Command Received" and Transition to Wait for Eff. Date State

See Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG sends command received acknowledgement to the 3rd party requester.

3.0 Evaluate Availability of Command Execution Date and TimeSee Manage Device Remote Connect (Echelon) Page 1 on page 2-2 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: If command's effective date and time is available, SGG uses it to determine execution date and time. If the effective Date and Time is not available, SGG processes the Outbound Communication immediately. If effective Date and Time is in the future System it waits in 'Wait for Effective Date' state, else, it processes the Outbound Communication.

Entities to Configure

To Do Type

To Do Role

Business Objects Available Algorithms

D1-RemoteConnectD1-RemoteConnectType

D1-CTDEBOE (Create To Do Entry for BO in Error)

Entities to Configure

Processing Role

Business Objects Available Algorithms

D1-RemoteConnect D1-RRER (Send Received Response to External Requester)

Customizable Processes

D1-CRWT (Command Request Wait - Monitor)

2-24 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 33: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

3.1 Review Activity in Eff. Date StateSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User reviews and analyzes the Activity.

3.2 Request to Delete ActivitySee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: If MDM or SGG Authorized User determines that the Activity is not required, Authorized User requests to delete Activity record.

3.3 Delete ActivitySee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG deletes the Activity.

Note: Once an Activity record is deleted it is permanently removed from the system and cannot be recovered. This option is not recommended for common business practice.

Entities to Configure

Effective Date and Time

Business Objects Available Algorithms

D1-RemoteConnect D1-WAITEFFDT (Wait for Effective Date)F1-AT-RQJ (Transition to Default Next Status (Java))

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

Detailed Business Process Model Description 2-25

Page 34: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

3.4 Request to Discard ActivitySee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User if determines that the Activity is not required, Authorized User requests to discard it.

3.5 Populate Changes and Request to UpdateSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User modifies Activity data and requests to perform appropriate updates.

3.6 Update ActivitySee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG updates the Activity with data populated by Authorized User.

3.7 Request to Connect DeviceSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

2-26 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 35: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Description: If command's effective date and time is in the future and MDM or SGG Authorized User identifies the need to execute command immediately, Authorized User requests to initiate the command processing.

3.8 Transition Activity to Connection Ready StateSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions the Activity to 'Connection Ready' state to initiate outbound communication when command effective date and time has reached. The other possible option of transition and initiation is when the Authorized User manually makes a request.

3.9 5.6.3.6b SGG-MDM.Manage Device Device Status Check (Echelon)See Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG determines the processing method for Device Status Check Outbound Communication and initiates status check. Please refer to process 5.6.3.6b SGG-MDM.Manage Device Device Status Check (Echelon) Command for further details.

Business Object

D1-RemoteConnect

Customizable Processes

D1-CRWT (Command Request Wait - Monitor)

Entities to Configure

Effective Date and Time

Business Objects Available Algorithms

D1-RemoteConnect D1-WAITEFFDT (Wait for Effective Date)

Business Objects Available Algorithms

D1-RemoteConnect D1-CLCOC (Create Load Check Outbound Communication)

Detailed Business Process Model Description 2-27

Page 36: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

4.0 Transition Activity to Connection Ready StateSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions the Activity to 'Connection Ready' state.

4.0.1 Evaluate Request if Meter Read is RequiredSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG evaluates and checks if there exists any request to retrieve measurement.

4.1 5.6.3.1b SGG-MDM.Manage On-Demand Read (Echelon)See Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG determines the processing method for Meter Read Outbound Communication and initiates Meter Read. Please refer to process 5.6.3.1b SGG-MDM.V2.0.0.Manage On-Demand Read (Echelon).Manage Outbound and Inbound Communication for further details.

4.2 Transition Activity to Connection Ready StateSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions the Activity to 'Connection Ready' state.

Business Object

D1-RemoteConnect

Business Objects Available Algorithms

D1-RemoteConnect D1-CODROC (Create On-Demand Read for Start Measurement)

Business Objects Available Algorithms

D1-RemoteConnect D1-CODROC (Create On-Demand Read for Start Measurement)

2-28 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 37: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

4.3 Transition Activity to Communication in Progress StateSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions Activity to 'Communication in Progress' state to monitor response for the outbound communication..

4.4 Evaluate Wait Period for ResponseSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG periodically checks if the Activity expiration wait time configured for monitoring the response has expired or not.

4.5 Transition Activity to Communication Error State and Log ErrorSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Business Object

D1-RemoteConnect

Business Objects Available Algorithms

D1-RemoteConnectl F1-AT-RQJ (Transition to Default Next Status)

Customizable Processes

D1-CRWT (Command Request Wait - Monitor)

Entities to Configure

Activity Type

Business Objects Available Algorithms

D1-RemoteConnect D1-WTTMOUTEX (Wait Time Out - Transition to Exception)

Detailed Business Process Model Description 2-29

Page 38: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Description: If the wait time for outbound communication response has expired, SGG transitions the Activity to 'Communication Error' state and logs an error.

4.6 Review Activity in Comm. In Progress StateSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User reviews and analyzes the Activity.

4.7 Request to Retry ActivitySee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User requests to recreate the Outbound Communication process.

4.8 Transition Activity to Retry StateSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions Activity to 'Retry' state.

4.9 Cancel Outstanding Outbound CommunicationSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

2-30 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 39: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Description: SGG cancels any existing outstanding Outbound Communications.

5.0 Initiate Remote Connect Outbound CommunicationSee Manage Device Remote Connect (Echelon) Page 2 on page 2-3 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG determines the processing method for Remote Connect Outbound Communication and initiates the Outbound Communication process.

5.1 Create Outbound Communication in Pending StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG creates Remote Connect Outbound Communication in 'Pending' state.

Business Objects Available Algorithms

D1-RemoteConnect D1-COOC (Cancel Outstanding Outbound Communication)

Entities to Configure

Outbound Communication Processing Method

Business Objects Available Algorithms

D1-RemoteConnect D1-CRCOC (Create Remote Connect Outbound Communication)

Entities to Configure

Outbound Communication Processing Method

Outbound Communication Type

Business Objects Available Algorithms

D4-ConnectLoad D1-CRCOC (Create Remote Connect Outbound Communication)D1-GDRFFPA (Default required fields from Parent Activity)

Detailed Business Process Model Description 2-31

Page 40: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

5.2 Validate Ability to Process Outbound Communication and Transition to Validate State

See Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG validates ability to process Outbound Communication. Typically, system checks for communication type.

5.3 Transition Outbound Communication to Validation Error State and Log Error

See Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: If any error occurs during validations, SGG transitions the Outbound Communication to 'Validation Error' state and logs an error.

5.4 Populate Connect Request Details and Transition to Awaiting Response State

See Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG transitions Outbound Communication to 'Awaiting Response' state and populates Remote Connect Outbound Communication message details.

Entities to Configure

Outbound Communication Type

Business Objects Available Algorithms

D4-ConnectLoad D1-VALCOMTP (Validate Communication Type)F1-AT-RQJ (Transition to Default Next Status)

Business Object

D4-ConnectLoad

2-32 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 41: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

5.5 Create and Send Outbound Communication Message to Echelon Head-End System

See Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG creates Outbound Communication and sends it to Head-End System.

5.6 Communicate and Transform Message to Echelon FormatSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Integration Layer (SGG BPEL)

Actor/Role: SGG

Description: Integration layer of SGG facilitates the communication between the SGG and Echelon Head-End System. It receives the Outbound Communication request, transforms, and converts the request into format compatible with Head-End System.

5.7 Receive and Process Request MessageSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: Head-End System

Description: Head-End System receives the Remote Connect request and processes it.

Note: This is external and outside the Oracle SGG environment.

Entities to Configure

Inbound Communication Processing Method

Business Objects Available Algorithms

D4-ConnectLoad D4-PCLRSD (Populate Connect Load Request Send Detail)

Business Objects Available Algorithms

D4-ConnectLoad D4-COUTMSGC (Create Outbound Message For Connect Load)

Detailed Business Process Model Description 2-33

Page 42: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

5.8 Receive and Process Device Connect RequestSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: Smart Meter

Description: Smart Meter Device receives request from Head-End System for Remote Connect and processes it.

Note: This is external and outside the Oracle SGG environment.

5.9 Analyze Message and Send AcknowledgementSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: Head-End System

Description: Head-End System on receipt of Remote Connect request from SGG, analyzes, and sends a real-time acknowledgement back to SGG.

6.0 Communicate and Transform Acknowledgement to SGG FormatSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Integration Layer (SGG BPEL)

Actor/Role: SGG

Description: Integration layer of SGG facilitates the communication between the Head-End System and SGG. It receives the synchronous acknowledge, transforms, and converts the acknowledgement into format compatible with SGG.

6.1 Evaluate Acknowledgement See Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG evaluates acknowledge and checks the success of sending Outbound Communication.

6.2 Log Error and Transition to Response Error StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Business Objects Available Algorithms

D4-ConnectLoad D4-EVALRESP (Evaluate Response)

2-34 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 43: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG logs error and transitions Outbound Communication to Response Error state.

6.3 Evaluate Wait Period for ResponseSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG periodically checks if the Outbound Communication expiration wait time configured for monitoring the response has expired or not.

6.4 Log Error and Transition to Response Error StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG logs error and transitions Outbound Communication to Response Error state.

Business Objects Available Algorithms

D4-ConnectLoad D4-EVALRESP (Evaluate Response)

Customizable Processes

D1-COMM (Batch Control for Communications)

Entities to Configure

Outbound Communication Type

Business Objects Available Algorithms

D4-ConnectLoad D1-TIMEOUT (Time Out)

Business Objects Available Algorithms

D4-ConnectLoad D1-TIMEOUT (Time Out)

Detailed Business Process Model Description 2-35

Page 44: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

6.5 Review Outbound CommunicationSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User reviews and analyzes the Outbound Communication.

6.6 Request to DiscardSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User if determines that the Outbound Communication is not required, Authorized User requests to discard it.

6.7 Transition Outbound Communication to Discard StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG transitions Outbound Communication to 'Discard' state.

Note: When an Outbound Communication is 'Discarded' it still remains in the system database and is not removed, hence, this is the preferred business practice to perform.

6.8 Populate Changes and Request to UpdateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Business Object

D4-ConnectLoad

Business Object

D4-ConnectLoad

Business Object

D4-ConnectLoad

2-36 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 45: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User modifies Outbound Communication data and requests to perform appropriate updates.

6.9 Update Outbound CommunicationSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG updates the Outbound Communication with data populated by Authorized User.

7.0 Request to RetrySee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User requests to recreate the Outbound Communication.

7.1 Transition Outbound Communication to Retry StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG transitions Outbound Communication to 'Retry' state.

Business Object

D4-ConnectLoad

Business Object

D4-ConnectLoad

Business Object

D4-ConnectLoad

Detailed Business Process Model Description 2-37

Page 46: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

o

7.2 Send Remote Connect Response to Echelon Head End SystemSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: Smart Meter

Description: Smart Meter Device sends response for the remote connect request received.

Note: This is external and outside the Oracle SGG environment.

7.3 Receive and Process Remote Connect Response to Echelon SGGSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: Head-End System

Description: Head-End System receives the response from Smart Meter and processes a response for SGG.

Note: This is external and outside the Oracle SGG environment.

7.4 Communicate and Transform Remote Connect Response to Echelon SGG Format

See Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Group: Integration Layer (SGG BPEL)

Actor/Role: SGG

Description: Integration layer of SGG facilitates the communication between the Head-End System and SGG. It receives the response, transforms, and converts the response into format compatible with SGG.

7.4.1 Identify Response Message and Processing MethodSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Business Object

D4-ConnectLoad

2-38 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 47: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Description: SGG identifies the inbound command completion event message and determines appropriate processing method.

Note: The SGG uses device event seeder to perform this action.

7.5 Pre-process Inbound MessageSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Description: SGG retrieves details from inbound communication and performs pre-processing.

7.6 Create Inbound Communication in Pending StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Description: SGG creates Inbound Communication in 'Pending' state.

Business Objects Available Algorithms

D1-DeviceEventSeeder D1-DVEVTINFO (Device Event Info)D1-SETERRFLG (Set Error Flag)D1-SPRID (Service Provider Identification)D1-DEVICEID (Device Identification)D1-SHEVTDTTM (Shift Event Date/Times to Standard)D1-DETBOID (Device Event Type and Business Object Identification)D1-SETBO (Set BO)

Business Objects Available Algorithms

D4-ConnectLoadNtf D1-COMMINFO (Communication Information)D4-SETDFBOEL (Set default BO elements)

Detailed Business Process Model Description 2-39

Page 48: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

7.7 Validate Ability to Process Inbound Communication and Transition to Validate State

See Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Description: SGG validates ability to process Inbound Communication. Typically, it checks for Communication Type, determines the outbound communication that initiated it and links to it and also evaluates the status of Remote Connect event success status.

7.8 Transition Inbound Communication to Validation Error State and Log ErrorSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Description: If any error occurs during validations, SGG transitions the Inbound Communication to 'Validation Error' state and logs an error.

Business Object

D4-ConnectLoadNtf

Entities to Configure

Inbound Communication Type

Business Objects Available Algorithms

D4-ConnectLoadNtf D1-VALCOMTP ( Validate Communication Type)D4-FPCOMMBO (Find Initiating Outbound Communication)D4-EVNSTAT (Evaluate Notification Status)F1-AT-RQJ (Transition to Default Next Status)

Business Object

D4-ConnectLoadNtf

2-40 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 49: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

7.9 Transition to Create Completion Event StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Description: SGG transitions Inbound Communication to 'Create Completion Event' state.

8.0 Validate and Create Device Connect Completion Event in Pending StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Description: SGG creates Connect Device Completion Event in 'Pending' state. SGG validates ability to process Connect Device Completion Event. Typically, it checks for Completion Event and its related Activity Type, Sequence number for Completion Events, etc.

8.1 Transition Inbound to Completed StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Description: SGG transitions Inbound Communication to 'Completed' state.

Business Objects Available Algorithms

D4-ConnectLoadNtf F1-AT-RQJ (Transition to Default Next Status (Java))

Business Objects Available Algorithms

D4-ConnectLoadNtfD1-Completion EventD1-ConnectDevice

D4-CCCE (Create Connect Completion Event)D1-CEVTINFO (Completion Event - Information)D1-VALCEVT (Validate Completion Event)D1-VALOUTCOM (Validate Outbound Communication)D1-VALTRCEVT (Validate Transition Completion Events)

Detailed Business Process Model Description 2-41

Page 50: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

8.2 Transition Outbound Communication to Completed StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Group: Inbound Communication Process

Actor/Role: SGG

Description: SGG transitions Outbound Communication to 'Completed' state and updates Event Date/Time.

8.3 Transition Activity to Execution Completion Event StateSee Manage Device Remote Connect (Echelon) Page 3 on page 2-4 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG Activity to 'Execution Completion Event' state. In this state, SGG transitions its Completion Events to 'Executed' state.

8.4 Transition Meter Read Completion Event to Executed StateSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Business Objects Available Algorithms

D4-ConnectLoadNtf F1-AT-RQJ (Transition to Default Next Status (Java))

Business Objects Available Algorithms

D4-ConnectLoadNtf D1-UPCMEVDTR (Update Parent Communication's Event Date Time Connect)D1-TRANPRBO (Transition Parent Outbound Communication BO)

Business Objects Available Algorithms

D4-ConnectLoadD1-CompletionEvent

D1-UCCDFTPA (Update Connect Disconnect Completion Flag and Transition Parent Activity)D1-EXCMPEVTS (Execute Completion Events)

2-42 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 51: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Actor/Role: SGG

Description: SGG transitions Create IMD Completion Event to 'Executed' state.

8.5 Preprocess IMDSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Group: Outbound Communication Process

Actor/Role: SGG

Description: SGG invokes to preprocess the IMD by invoking seeder preprocessing. Please refer to process 4.2.1.1 MDM.Upload Device Measurements for further details.

8.6 Transition Device Connect Completion Event to Executed StateSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions Connect Device Completion Event to 'Executed' state.

8.7 Update Device Install Event to 'Connect' StateSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG updates the install event state to Connect.

Business Objects Available Algorithms

D1-RemoteConnectD1-Completion EventD1-CreateIMD

D1-EXCMPEVTS (Execute Completion Events)

Business Objects Available Algorithms

D1-RemoteConnectD1-Completion EventD1-CreateIMD

D1-CREIMD (Create IMD)

Business Objects Available Algorithms

D1-RemoteConnectD1-Completion EventD1-Connect Device

D1-EXCMPEVTS (Execute Completion Events)

Detailed Business Process Model Description 2-43

Page 52: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

8.8 Transition Activity to Completion Event Error State and Log ErrorSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: If any errors are encountered while transitioning Completion Events to 'Executed' state, SGG transitions Activity to 'Completion Event Error' state and logs an error.

8.9 Transition Activity to Waiting for Measurement StateSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions Activity to 'Waiting for Measurement' state.

9.1 4.2.1.2 MDM.Manage VEE and VEE ExceptionsSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: MDM

Description: MDM performs the VEE processing of IMD created. Please refer to process 4.2.1.2 MDM.Manage VEE and VEE Exceptions for further details.

9.2 Retrieve and Store Final MeasurementsSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Business Objects Available Algorithms

D1-RemoteConnectD1-Completion EventD1-Connect Device

D1-CONNDEV (Connect Device)

Business Objects

D1-RemoteConnectD1-Completion EventD1-CreateIMDD1-Connect Device

Business Objects Available Algorithms

D1-RemoteConnect F1-AT-RQJ (Transition to Default Next Status (Java))

2-44 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 53: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Description: SGG retrieves final measurements and stores as Meter Read on Activity.

9.3 Retrieve and Store Initial MeasurementsSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG retrieves IMD measurement and stores as Meter Read on Activity. Depending on the state of IMD measurement availability in the system, SGG has various options of retrieving IMD.

9.4 Monitor IMD Availability within Allowable PeriodSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG monitors if the IMD measurement becomes available in allowable window period.

Customizable process

D1-CRWT (Command Request Wait - Monitor)

Business Objects Available Algorithms

D1-RemoteConnect D1-RFINSC (Retrieve Scalar Final Measurements)

Customizable process

D1-CRWT (Command Request Wait - Monitor)

Business Objects Available Algorithms

D1-RemoteConnect D1-RMVCE (Retrieve Measurements via Completion Events)D1-RSINIMS (Retrieve Scalar Initial Measurements)

Customizable process

D1-CRWT (Command Request Wait - Monitor)

Detailed Business Process Model Description 2-45

Page 54: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

9.5 Transition Activity to Wait Expired Error State and Log ErrorSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: If IMD is not available within the Wait time and it expires, SGG transitions Activity to 'Wait Expired' state and logs an error.

9.6 Review Activity Waiting for MeasurementSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User can review and analyze the Activity.

9.7 Request to CompleteSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: While the Activity is in 'Waiting for Measurement' state, MDM or SGG Authorized User can process the Activity immediately by making a manual 'Request to Complete' to SGG.

Entities to Configure

Activity Type

Business Objects Available Algorithms

D1-RemoteConnectD1-RemoteConnectType

D1-WFMTO (Wait for Measurement Time Out)

Entities to Configure

Activity Type

Business Objects Available Algorithms

D1-RemoteConnectD1-RemoteConnectType

D1-WFMTO (Wait for Measurement Time Out)

Business Object

D1-RemoteConnect

2-46 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 55: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

9.8 Transition Activity to Completion StateSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions Activity to 'Completed' state.

9.9 Create and Send Connect Success Notification to RequesterSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG creates the message and sends Connect Device success notification to Requester based on the processing method.

10.0 Create and Send Meter Read to RequesterSee Manage Device Remote Connect (Echelon) Page 4 on page 2-5 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG creates the message and sends Meter Read message to Requester based on the processing method.

Business Object

D1-RemoteConnect

Business Objects Available Algorithms

D1-RemoteConnect F1-AT-RQJ (Transition to Default Next Status (Java))

Business Objects Available Algorithms

D1-RemoteConnect D1-SRCNTEA (Send Remote Connect Notification to Edge Application)

Business Objects Available Algorithms

D1-RemoteConnect D1-SODRTEA (Send Start Measurement to Edge Application)

Detailed Business Process Model Description 2-47

Page 56: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

10.1 Transition Activity to Discard StateSee Manage Device Remote Connect (Echelon) Page 5 on page 2-6 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG transitions Activity to 'Discard' state indicating that it cannot be further used. However, it remains in the system.

10.2 Cancel Outstanding Completion EventsSee Manage Device Remote Connect (Echelon) Page 5 on page 2-6 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: When Activity is discarded, SGG cancels any existing outstanding Completion Events.

10.3 Send Response “Command Failed” to RequesterSee Manage Device Remote Connect (Echelon) Page 5 on page 2-6 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG creates the message and sends Meter Read message to Requester based on the processing method.

10.4 Analyze Requirements to Create EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User analyzes requirements and gathers information required to create Connect Device Completion Event.

Business Objects Available Algorithms

D1-RemoteConnect D1-TPATOF (Transition Parent Activity To Failed)

Business Objects Available Algorithms

D1-RemoteConnect D1-COCE (Cancel Outstanding Completion Events)

Business Objects Available Algorithms

D1-RemoteConnect D1-FRER (Send Fail Response to External Requester)

2-48 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 57: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Note: In general, creating Connect Device Completion Event manually is not the practical business practice.

10.5 Select Completion Event Type and Populate DataSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User selects the event type as Connect Device Completion Event and populates the required data.

10.6 Request to Create Completion EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User makes a request to SGG to create Connect Device Completion Event.

10.7 Review EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User can review and analyze the Connect Device Completion Event created.

10.8 Request to Delete EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User if determines that the Connect Device Completion Event is not required, Authorized User requests to delete it.

Business Object

D1-Completion EventD1-Connect Device

Detailed Business Process Model Description 2-49

Page 58: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

10.9 Delete Completion EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: SGG

Description: SGG deletes the Connect Device Completion Event.

11.0 Request to Discard EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User if determines that the Connect Device Completion Event is not required, Authorized User requests to discard it.

11.1 Transition to Discard State and Discard Completion EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: SGG

Description: SGG transitions Connect Device Completion Event to 'Discard' state.

Business Object

D1-Completion EventD1-Connect Device

Business Object

D1-Completion EventD1-Connect Device

Business Object

D1-Completion EventD1-Connect Device

Business Object

D1-Completion EventD1-Connect Device

2-50 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 59: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

11.2 Request to Update EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User modifies Connect Device Completion Event data and requests to perform appropriate updates.

11.3 Update Completion EventSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: SGG

Description: SGG updates the Connect Device Completion Event with data populated by Authorized User.

11.4 Request to ExecuteSee Manage Device Remote Connect (Echelon) Page 6 on page 2-7 for the business process diagram associated with this activity.

Group: Manual Connect Device Completion Event Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User requests to transition Connect Device Completion Event to 'Executed' state.

11.5 Gather Requirements to Cancel CommandSee Manage Device Remote Connect (Echelon) Page 7 on page 2-8 for the business process diagram associated with this activity.

Business Object

D1-Completion EventD1-Connect Device

Business Object

D1-Completion EventD1-Connect Device

Business Object

D1-Completion EventD1-Connect Device

Detailed Business Process Model Description 2-51

Page 60: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User analyzes requirements and gathers information required to cancel Remote Connect command.

11.6 Select Cancel Command Activity TypeSee Manage Device Remote Connect (Echelon) Page 7 on page 2-8 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User selects Activity Type as 'Cancel Command' to cancel Connect command request.

11.7 Populate Cancel Command Execution DataSee Manage Device Remote Connect (Echelon) Page 7 on page 2-8 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User populates the required data such as request expiration date, recipient information, etc.

11.8 Communicate and Transform Remote Connect Cancel Command to SGG Format

See Manage Device Remote Connect (Echelon) Page 7 on page 2-8 for the business process diagram associated with this activity.

Actor/Role: Integration Layer

Description: Integration layer facilitates the communication between the 3rd Party application and the SGG application. It receives the Cancel Command request, transforms, and converts the request into format compatible with SGG application.

11.9 Identify Remote Connect Activity based on Transaction IDSee Manage Device Remote Connect (Echelon) Page 7 on page 2-8 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG identifies the Remote Connect Activity to cancel based on the transaction ID, which was created in SGG when the request originally came from 3rd party application and sent later to 3rd party application. However, in case of manual request from Authorized User, the Activity is identified based on manual selection while populating the required data for cancel command request.

12.0 Analyze Error and Work To DoSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User analyzes the error logged and respective To Do created to determine the corrective action and to perform work.

2-52 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 61: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

.

12.1 Request to DeleteSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: MDM or SGG Authorized User

Description: If MDM or SGG Authorized User determines that the Inbound Communication is not required, Authorized User can request to delete it.

.

12.2 Delete Inbound CommunicationSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: SGG

Description: SGG deletes Inbound Communication.

.

12.3 Request to DiscardSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: MDM or SGG Authorized User

Description: MDM or SGG Authorized User, if determines that the Inbound Communication is not required, Authorized User can request to discard it.

.

Business Object

D1-RemoteConnectD4-ConnectLoadD4-ConnectLoadNtf

Business Object

D4-ConnectLoadNtf

Business Object

D4-ConnectLoadNtf

Business Object

D4-ConnectLoadNtf

Detailed Business Process Model Description 2-53

Page 62: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

12.4 Complete To Do(s)See Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Actor/Role: SGG

Description: SGG finds all non-completed To Do entries and completes them.

12.5 Transition Inbound Communication to Discard StateSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: SGG

Description: SGG transitions Inbound Communication to 'Discard' state

.

12.6 Log Error and Transition Outbound Communication to Response Error State

See Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: SGG

Description: SGG logs error and transitions Outbound Communication to Response Error state.

12.7 Request to ValidateSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: MDM or SGG Authorized User

Business Objects Available Algorithms

D1-RemoteConnectD4-ConnectLoadD4-ConnectLoadNtf

D1-GTDCBO ( Generic To Do Completion for BOs)

Business Object

D4-ConnectLoadNtf

Business Objects Available Algorithms

D4-ConnectLoadNtf D1-FAILPCOUT (Fail Parent Outbound Activity)

2-54 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 63: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Description: If Authorized User wants to reprocess the inbound communication, can request to validate it.

12.8 Transition to Validate State and Initialize ReprocessingSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: SGG

Description: SGG transitions Inbound Communication to 'Validate' state and initializes reprocessing.

12.9 Identify Inbound Communication in Validation Error StateSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: SGG

Description: SGG identifies Inbound Communication in 'Validation Error' state.

13.0 Evaluate Criteria to Run Automated Retry ProcessSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Inbound Exception Process

Actor/Role: SGG

Description: SGG evaluates criteria to run automated retry process. A Batch process is configured for this.

Business Object

D4-ConnectLoadNtf

Business Objects Available Algorithms

D4-ConnectLoadNtf D1-RBOE (Retry BO in Error)

Customizable Process

D1-ICERR (Inbound Communication Error - Retry)

Business Object

D4-ConnectLoadNtf

Detailed Business Process Model Description 2-55

Page 64: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Note: If Business requires different criteria to retry the process, those criteria could be configured in parameter section of batch process.

13.1 Request to DeleteSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Outbound Exception Process

Actor/Role: MDM or SGG Authorized User

Description: If MDM or SGG Authorized User determines that the Outbound Communication is not required, Authorized User can request to delete it.

13.2 Delete Outbound CommunicationSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Outbound Exception Process

Actor/Role: SGG

Description: SGG deletes Outbound Communication from the system.

13.3 Request to ValidateSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Outbound Exception Process

Customizable Process

D1-ICERR (Inbound Communication Error - Retry)D1-OCERR (Outbound Communication Error - Retry)D1-CRERR (Command Request Error - Retry)

Business Object

D1-RemoteConnectD4-ConnectLoadD4-ConnectLoadNtf

Business Object

D4-ConnectLoad

Business Object

D4-ConnectLoad

2-56 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 65: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Actor/Role: MDM or SGG Authorized User

Description: If Authorized User wants to reprocess the Outbound Communication, can request to validate it.

13.4 Transition to Validate State and Initialize ReprocessingSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Outbound Exception Process

Actor/Role: SGG

Description: SGG transitions Outbound Communication to 'Validate' state and initializes reprocessing.

13.5 Identify Outbound Communication in Validation Error StateSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Outbound Exception Process

Actor/Role: SGG

Description: SGG identifies Outbound Communication in 'Validation Error' state.

13.6 Transition Outbound Communication to Retry StateSee Manage Device Remote Connect (Echelon) Page 8 on page 2-9 for the business process diagram associated with this activity.

Group: Outbound Exception Process

Actor/Role: SGG

Business Object

D4-ConnectLoad

Business Objects Available Algorithms

D4-ConnectLoadNtf D1-RBOE (Retry BO in Error)

Customizable Process

D1-OCERR (Outbound Communication Error - Retry)

Business Object

D4-ConnectLoad

Detailed Business Process Model Description 2-57

Page 66: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Description: SGG transitions Outbound Communication to 'Retry' state and initializes reprocessing.

13.7 Identify Outbound Communication in Response Error StateSee Manage Device Remote Connect (Echelon) Page 9 on page 2-10 for the business process diagram associated with this activity.

Group: Outbound Exception Process

Actor/Role: SGG

Description: SGG identifies Outbound Communication in 'Response Error' state.

13.8 Request to RevalidateSee Manage Device Remote Connect (Echelon) Page 9 on page 2-10 for the business process diagram associated with this activity.

Group: 'Validation Error' Exception Process

Actor/Role: MDM or SGG Authorized User

Description: If Authorized User wants to reprocess the Activity, can request to validate it.

13.9 Transition Activity to Validate State and Initialize ReprocessingSee Manage Device Remote Connect (Echelon) Page 9 on page 2-10 for the business process diagram associated with this activity.

Group: 'Validation Error' Exception Process

Actor/Role: SGG

Description: SGG transitions Activity to 'Validate' state and initializes reprocessing.

Business Objects Available Algorithms

D4-ConnectLoadNtf D1-RBOE (Retry BO in Error)

Customizable Process

D1-OCERR (Outbound Communication Error - Retry)

Business Object

D4-ConnectLoad

Business Object

D1-RemoteConnect

2-58 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 67: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

14.0 Identify Activity in Validation Error StateSee Manage Device Remote Connect (Echelon) Page 9 on page 2-10 for the business process diagram associated with this activity.

Group: 'Validation Error' Exception Process

Actor/Role: SGG

Description: SGG identifies Activity in 'Validation Error' state.

14.1 Transition Activity to Retry StateSee Manage Device Remote Connect (Echelon) Page 9 on page 2-10 for the business process diagram associated with this activity.

Group: ''Communication Error' Exception Process

Actor/Role: SGG

Description: SGG transitions Activity to 'Retry' state.

14.2 Identify Activity in Communication Error StateSee Manage Device Remote Connect (Echelon) Page 9 on page 2-10 for the business process diagram associated with this activity.

Group: ''Communication Error' Exception Process

Actor/Role: SGG

Description: SGG identifies Activity in 'Communication Error' state.

Business Objects Available Algorithms

D4-ConnectLoadNtf D1-RBOE (Retry BO in Error)

Customizable Process

D1-CRERR (Command Request Error - Retry)

Business Object

D1-RemoteConnect

Business Objects Available Algorithms

D1-RemoteConnect D1-RBOE (Retry BO in Error)

Detailed Business Process Model Description 2-59

Page 68: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

14.3 Request to Execute Completion EventSee Manage Device Remote Connect (Echelon) Page 10 on page 2-11 for the business process diagram associated with this activity.

Group: ''Communication Error' Exception Process

Actor/Role: MDM or SGG Authorized User

Description: If Authorized User wants to reprocess the Activity, can request to execute Completion Event.

14.4 Transition Activity to Execution Completion Event State and Initialize Reprocessing

See Manage Device Remote Connect (Echelon) Page 10 on page 2-11 for the business process diagram associated with this activity.

Group: ''Completion Event Error' Exception Process

Actor/Role: SGG

Description: SGG transitions Activity to 'Execution Completion Event' state and initializes reprocessing.

14.5 Identify Activity in Completion Event Error StateSee Manage Device Remote Connect (Echelon) Page 10 on page 2-11 for the business process diagram associated with this activity.

Group: ''Completion Event Error' Exception Process

Actor/Role: SGG

Description: SGG identifies Activity in 'Completion Event Error' state.

Customizable Process

D1-CRERR (Command Request Error - Retry)

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

Business Objects Available Algorithms

D1-RemoteConnect D1-RBOE (Retry BO in Error)

2-60 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 69: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

14.6 Request to Continue WaitingSee Manage Device Remote Connect (Echelon) Page 10 on page 2-11 for the business process diagram associated with this activity.

Group: 'Wait Expired Error' Exception Process

Actor/Role: MDM or SGG Authorized User

Description: If Authorized User wants to reprocess the Activity, can request to continue waiting.

14.7 Transition Activity to Waiting for Measurement State and Initialize Reprocessing

See Manage Device Remote Connect (Echelon) Page 10 on page 2-11 for the business process diagram associated with this activity.

Group: 'Wait Expired Error' Exception Process

Actor/Role: SGG

Description: SGG transitions Activity to 'Waiting for Measurement' state and initializes reprocessing.

14.8 Identify Activity in Wait Expired Error StateSee Manage Device Remote Connect (Echelon) Page 10 on page 2-11 for the business process diagram associated with this activity.

Group: 'Wait Expired Error' Exception Process

Actor/Role: SGG

Description: SGG identifies Activity in 'Wait Expired Error' state.

Customizable Process

D1-CRERR (Command Request Error - Retry)

Business Object

D1-RemoteConnect

Business Object

D1-RemoteConnect

Business Objects Available Algorithms

D1-RemoteConnect D1-RBOE (Retry BO in Error)

Detailed Business Process Model Description 2-61

Page 70: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Manage Device Remote Connect (Echelon) Description

Customizable Process

D1-CRERR (Command Request Error - Retry)

Business Objects Available Algorithms

D1-RemoteConnect D1-RBOE (Retry BO in Error)

2-62 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 71: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Objects Lifecycle

Business Objects Lifecycle

D1-RemoteConnect

Detailed Business Process Model Description 2-63

Page 72: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Objects Lifecycle

D4-ConnectLoad

2-64 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)

Page 73: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Objects Lifecycle

D4-ConnectLoadNtf

Detailed Business Process Model Description 2-65

Page 74: Oracle Utilities SGG V2.0.0 and MDM V2.0.1 Integrations · application), makes a request for a Device Remote Connect or a MDM or SGG Authorized User manually requests for a Device

Business Objects Lifecycle

D1-Completion Event

2-66 5.6.3.4b SGG-MDM.Manage Device Remote Connect (Echelon)