My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25H - AGMT FOR METER READING AND MANAGEMENT
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2020
>
11/17/2020
>
25H - AGMT FOR METER READING AND MANAGEMENT
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/12/2020 5:27:31 PM
Creation date
11/12/2020 3:23:03 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Finance & Management Services
Item #
25H
Date
11/17/2020
Destruction Year
2025
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
212
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
• A new button will be added to the account summary screen on a customer's WebConnect <br />account bringing them to SmartWorks Connect portal. <br />• Only accounts with AMI meter types will see this option <br />• This will be Single Sign on, when the customer log into WebConnect, they will not be <br />required to log in again to access SmartWorks Connect. <br />• A new window will be opened when the user clicks on this new option. <br />5.5.7. See Appendix A for sample SOAP Messages for enQuesta Interval Data requests. <br />5.6.On Demand Reading Request <br />5.6.1. enQuesta to perform on -demand read through MDMS MultiSpeak®® method <br />InitiateMeterReadingsByMeterID supplying a transaction ID and a response URL. <br />MDMS will then attempt to perform an on demand read to that meter, using whatever <br />protocol is configured for that action. This may be another MultiSpeak® request, but may <br />also be a proprietary API call depending on the AMI system the meter belongs to. Once <br />MDMS has received the readings from the AMI system, it will make a <br />ReadingChangedNotification call back to the response URL supplied in the initial request, <br />and quoting the supplied transaction ID. In the event of a timeout or other failure of the on - <br />demand reading, MDMS will respond with a MultiSpeak® error message. enQuesta will <br />make this process pseudo synchronous so the client processes stay the same. enQuesta will <br />have configuration to define how the reading will be acquired, by default it will use above <br />method but in case if there are communication problem with meter two other options will be <br />available: Using GetLatestReadingByMeterID method which asks for the most recent <br />2 5 H -116 Page 109 <br />
The URL can be used to link to this page
Your browser does not support the video tag.