This blog is about Meter Data Management System, NOC Application Layer as per International Standards IEC 61968-9 in Advanced Metering Infrastructure. Main Points to be discussed here
NOC Application Layer, IEC 61968-9
Meter Data Management System (MDM
This component operates within the NOC Application Layer, providing the interface between various HES and other back-office applications and SCADA. It should be capable of undertaking complex data processing tasks within very short time-frames.
1. Basic Technical Specifications
1. Data Repository and Historian
The Meter Data Management System shall:
● Have historian capability for a pre-agreed number of data points; providing long-term storage, with time reference, for all metered data, alarms and events it receives.
● Retain previous firmware revisions for the following AMI items:
o Smart Meters (End-Customer Application Layer)
o DCUs (Data Concentrator Application Layer)
● Data must be accessible to data processing applications (hosted by the MDM or supplementary servers) in very short time-frames.
2. Data Analysis
The eter Data Management shall provide the following functionality:
● Data Validation, Estimation and Editing (VEE)
● Trend Identification and Analysis
3. Time-of-Use (ToU) Pricing Function
The Meter Data Management System shall:
● Be able to transmit pricing information to Data Concentrators downstream in the AMI, within the associated WAN (Solution A), via the HES.
or
● Be able to transmit pricing information to household customers downstream in the AMI and within the associated WAN (Solution B), via the HES.
● Be capable of processing complex pricing algorithms, including pre-pay customers, to apportion cost (according to tariff) to metered data profiles received.
● Receive and store (locally) pricing information in the form of XML-based data tables
● Be able to assign financial value to each household’s consumption and micro-generation according to the metered data received across the WAN.
● Be able to store week-ahead tariff settings that can be communicated to home users upon scheduling the use of one or more of their appliances through their IHD.
● Be able to stream dynamic pricing to devices in the field, if required.
4. Interoperability
The Meter Data Management System shall:
● Support IEC 61968-9
● Offer easy integration with the Utility’s Enterprise Software (e.g., SAP) for functions such as CRM billing, etc., i.e., MDUS architecture for the AMI is mandated.
● Adopt Common Interface Model (CIM) formats in interactions with connected systems, e.g., for the delivery of CRM Billing Information.
2. Operational Requirements
1. Device Reliability
A. Standard Requirements
The Meter Data Management System shall be:
● Manufacturer guaranteed for a usage period of at least 10 years.
B. Diagnostics
The MDM shall:
● Be capable of performing a self-test (initiated either remotely or via secure, direct, physical interaction).
C. Firmware Requirements
The Meter Data Management System shall:
● Be capable of receiving and installing a firmware update (initiated either remotely or via direct local access) without having to power down.
● Retain one previous version of firmware (non-active) as a local back-up.
● Autonomously revert from the default firmware version to the back-up in the event that the default version is corrupted (e.g., just after a new version has been uploaded).
● Schedule firmware updates for DCUs and Smart Meters, within the NAN (Solution A, indirectly via the Data Concentrator Layer) or the WAN (Solution B).
D. Hardware Resets
The DCU shall:
● Retain any static data indefinitely whilst off supply.
2. Data Collection
The MDM shall:
● Handle the registration of all HES connected to it.
● Be capable of processing data from several different AMI components, e.g., multiple metering systems and associated HES.
● Facilitate remote data logging, via direct, secure access to locally stored meter data.
● Process the following information obtained from the AMI:
o Outage Alarms
o Tamper Alarms
o Demand Response Events
3. Time-Synchronization
The MDM shall:
● Possess an internal clock, synchronized with the AMI’s GPS-based, central timestamp.
● Co-ordinate time synchronization of all other components in the AMI.
Legacy Systems
This component will be implemented irrespective of the AMI (Advanced Metering Infrastructure) requirements and shall have its own distinct requirements. However, the nature of systems such as Enterprise Software must be taken into account before specifying any of the other AMI (Advanced Metering Infrastructure) components.
All article related to Smart Metering Technology are linked below step by step.
Advanced Metering Infrastructure | Smart Metering Technology
Advanced Metering Infrastructure Functionality – AMI Functions
Advanced Metering Infrastructure System Design Architecture
Advanced Metering Infrastructure Components
Advanced Metering Infrastructure Functional Requirements
Domestic Smart Meter Installation – ANSI 12.20 Electricity Meters
Data Concentrator Unit | DCU Principle with Technical Specification
Head End System for Advance Metering Infrastructure
Meter Data Management System – IEC 61968-9
Wireless Communications Principles and Industrial Practice