1 / 29

Monitoring Overall Read Performance RNI Release 3.1 SP2

Monitoring Overall Read Performance RNI Release 3.1 SP2. C-PAMRAMI-E-0131-01. Introduce the process and tools required to monitor the overall read performance of a FlexNet system. The goal of this module is to:.

grady
Download Presentation

Monitoring Overall Read Performance RNI Release 3.1 SP2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Monitoring Overall Read Performance RNI Release 3.1 SP2 C-PAMRAMI-E-0131-01

  2. Introduce the process and tools required to monitor the overall read performance of a FlexNet system. The goal of this module is to:

  3. Identify and use selected system statistics to evaluate the read performance of the system. • Determine the overall throughput of the system. • Identify trends in read performance and throughput. • View the deployed meters on a map. Module Objectives

  4. Review: Verifying Overall Read Performance Monitoring Overall Read Performance Are you receiving the expected number of reads in the last hour/day/week/month? Is the read performance trending down over time? Are meters providing billing reads? Are the readings stale? Are there alarms related to meter or Base Station communications? 1 Read Perf

  5. Monitoring Read Performance Using FlexWare Monitoring Overall Read Performance

  6. Monitoring Read Success: Steps 1-3 Monitoring Overall Read Performance Open an Internet Explorer session Enter the address of the FlexNet Web server Enter your username and password to open the FlexWare user interface

  7. Monitoring Read Success: Step 4 Monitoring Overall Read Performance Navigate to Diagnostics > Overall System Statistics

  8. Monitoring Read Success: Step 5 Monitoring Overall Read Performance Using the top row (OVERALL), compare the RIS % and Daily RIS % values. • The Read Interval Success Percentage is a calculation of the number of read intervals received divided by the number of read intervals expected, for the last 30 days • The Daily RIS % is the same, but for only the last 24 hours Quarantined meters are not included in RIS calculations

  9. Monitoring Read Success: Step 6 Monitoring Overall Read Performance Evaluate the data: • If the percentages are within normal range for your deployment, continue to next step • If not (or you choose to investigate further), look down through the various cities to find any bad performers • Daily good, but monthly not so good? • Probably old issue that has been resolved • Daily is bad, but monthly is good? • Likely a new issue; may need to investigate Overall By city

  10. Monitoring Read Success: Step 7 Monitoring Overall Read Performance Compare the Last TTM Hrs and Last Read Hrs values: • Indicate when getting reads may have become an issue • Last TTM Hrs: Length of time since last transmission received from an endpoint • Last Read Hrs: Length of time since last read loaded for an endpoint

  11. Monitoring Read Success: Step 7 (Continued) Monitoring Overall Read Performance If Last Read Hrs is larger than Last TTM Hrs, but both are small relative to the sample rate: • This is normal, continue to next step If the hours are bothlargeand nearly equal: • There is at least one location with issues providing reads • Look down the rows for potential cities to investigate further • Continue to next step

  12. Monitoring Read Success: Step 8 Monitoring Overall Read Performance Look at the Hr Stales value: • Indicates scope of the read problem • HR Stales: Number of meters that have not provided an updated read value in the specified timeframe Select the timeframe to view from the drop-down list

  13. Monitoring Read Success: Step 8 (Continued) Monitoring Overall Read Performance If the Hrs Stale number is small • Likely only an intermittent communication problem that might correct itself • Optionally you could further investigate the individual meters for issues If the Hrs Stale number is large • Likely more significant communication problem that should be investigated • Are the meters geographically together or do they have similar geographical issues that suggest an RF issue? • Do they have specific alarms to be remedied? • Is a Base Station down? Overall (total) By city

  14. Monitoring the Read Success Trend Monitoring Overall Read Performance 1. Click System Graphs 4. Adjust view 2. Select one or more cities to view 5. Analyze trend:Good = relatively flat or rising slightlyNot so good = trending downward, further investigation is required 3. Click RIS

  15. Monitoring Read Performance Using FlexWare Monitoring Overall Read Performance

  16. Monitoring Throughput: Step 1 Monitoring Overall Read Performance From the Diagnostics > Overall System Statistics page, click the Message Counts tab • This table shows a series of message counts and selected alarm flags that have occurred in the system in the last 24 hours and over the last 30 days

  17. Monitoring Throughput: Step 2 Monitoring Overall Read Performance Locate the Data Containing row which includes the messages that contain read data

  18. Monitoring Throughput: Step 3 Monitoring Overall Read Performance Multiply the Last 24 Hours valueby 30. Does it come close to the Last 30 Days value? • Yes • Great! Your message count (and by inference your read performance) is steady. • No • Last 24 Hours x 30 greater thanLast 30 Days: • If you are currently deploying FlexNet, you are getting more messages because more meters are being installed and sending messages. • If you are in production, you’ve experienced an increase in message traffic which may be effecting the network throughput. • Last 24 Hours x 30 less thanLast 30 Days: • Indicates a potential communications issue. Investigate accordingly.

  19. Monitoring Throughput Trend Monitoring Overall Read Performance 1. Click System Graphs 4. Adjust view 2. Select one or more cities to view 5. Analyze trend: Good = relatively flat or rising slightlyNot so good = trending downward, further investigation is required 3. Click Throughput

  20. Monitoring Read Performance Using FlexWare Monitoring Overall Read Performance

  21. Monitoring Read Performance Alarms: Step 1 Monitoring Overall Read Performance View Event Log for alarms that might impact the system’s ability to perform meter reads Click Reports > Event Log

  22. Monitoring Read Performance Alarms: Step 2 Monitoring Overall Read Performance For electric meters, filter for: • Power failures • Meter read failures • Single phase failures • Meter tamper • High temperature • Reverse energy • No meter

  23. Which of the following statistics is useful for determining the overall read performance of the system? • Last Read Hours • Read Interval Success • Hours Stale • All of the above

  24. Describe how to obtain the Read Interval Success graph below and analyze the results.

  25. Which of the following best describes the meaning of the Hrs Stale statistic? • Number of hours during which a meter has not communicated a read • Number of hours for which the meter has produced reads and sent to Base Station • Number of meters that have not provided an updated read during the specified hours • None of the above

  26. Which of the following might indicate an issue that impacts the system read performance? • Both the Last Read Hrs and Last TTM are small • Both the Last Read Hrs and Last TTM are large • The Last Read Hrs is smaller than the Last TTM, but within the sample rate • All of the above

  27. Which diagnostics report is used to compare the daily and monthly overall throughput for the system? • Message Counts • System Stats • Tower Stats • Missed Messages

  28. What would a normal system throughput graph look like? • Decreasing over time • Increasing rapidly over time • Periodic spikes and dips over time • Relatively flat over time

More Related