No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CLI-based Configuration Guide - AMI

AR500, AR510, AR531, AR550, AR1500, and AR2500 V200R010

This document describes the principles and configurations of the AMI features, and provides configuration examples of these features.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Data Collection

Data Collection

Meter Data Collection

The device collects meter data using real-time meter data reading, periodic meter data reading, and supplementary meter data reading. Meter data includes real-time data, historical data, and event data. Historical data includes load curve data, hourly frozen data, daily frozen data, and monthly frozen data.

The three meter data collection modes are described as follows:
  • Real-time meter data reading
    Figure 1-2  Real-time meter data reading process

    Figure 1-2 illustrates the real-time meter data reading process.
    • Step 1: A front-end processor delivers a real-time meter data reading instruction to the device (DCU in Figure 1-2).
    • Step 2: The device receives the instruction from the front-end processor, generates a communication packet in compliance with a meter protocol based on the instruction, and sends the packet to the meter.
    • Step 3: The meter returns the meter data reading result to the device within the specified time. For example, the timeout period of an HI-PLC channel is 15s.
    • Step 4: The device sends the result to the front-end processor, and the front-end processor receives meter data.
      NOTE:

      In most cases, a meter returns the meter data reading result to the device within 500 ms. If the device does not receive the meter data reading result from the meter in a timely manner, the meter can re-collect meter data. You can set the re-collection interval for meter data. If the configured time exceeds 20s, you also need to change the default meter data reading timeout period of the front-end processor. The meter data reading timeout period of the front-end processor must be two times longer than the re-collection interval for meter data.

    Purposes of real-time meter data reading are:

    • Determine connectivity of data collection channels

      The device determines whether a data collection channel is working properly based on the status of meters connected to a collection channel. If data cannot be collected on one meter but other meters are working properly, only this meter is faulty.

    • Verify data

      If some of the historical meter data is suspected to be incorrect, data collected through real-time meter data reading can help verify the historical data.

  • Periodic meter data reading

    Figure 1-3  Periodic meter data reading process

    Figure 1-3 illustrates the periodic meter data reading process.
    • Step 1: The device (DCU in Figure 1-3) obtains the configuration of a scheduled task, generates a periodic meter data reading task, and reads frozen data stored in meters. Periodic meter data reading is triggered by a timer in the device.
    • Step 2: The meters return results to the device.
    Table 1-1 lists types of data collected by the scheduled task.
    Table 1-1  Types of data collected by the scheduled task

    Type

    Description

    Daily frozen data

    Daily frozen record that a device periodically collects from meters

    Monthly frozen data

    Monthly frozen record that a device periodically collects from meters

    Hourly frozen data

    Hourly frozen record that a device periodically collects from meters

    Curve frozen data

    Frozen record that a device collects from meters

    Meter event

    Meter event detection that determines whether data is abnormal. If data is abnormal, an event is generated.

  • Supplementary meter data reading

    The device reads meter data that is not read by periodic meter data reading tasks, when the collection channel is idle.

    The device can periodically read data from meters where data is not collected daily. The data includes curve frozen data, hourly frozen data, daily frozen data, monthly frozen data, and data that fails to be collected during event collection tasks.

Status Collection

The device collects status changes that occur when the meter box, terminal cover, or meter cover is opened. Meter box opening is used as an example to describe how the device collects, stores, analyzes, and processes status data.

The device is installed in a meter box and provides real-time monitoring for the meter box. This function prevents meter data from being modified.

  1. When the meter box is opened or closed, an open or close signal is generated.
  2. The device monitors open or close signals in real time, and stores status change information.
  3. The device reports the meter box status to the front-end processor, and the front-end processor reports the meter box status to the EDM for exception analysis. The front-end processor can also periodically query meter status change information. The meter status change information helps you determine whether the meter box has been opened normally or maliciously.
Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100034224

Views: 10479

Downloads: 20

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next