This article is about Head End System for Advance Metering Infrastructure where we will discuss Head End System Architecture and Head End System AMI in plants and industries. Now Question is ”What is a Head End System” and Head End System Definition.
Head End System for Advance Metering Infrastructure
What is a Head End System, Head End System Definition
A head-end system is hardware and software that receives the stream of meter data brought back to the utility through the AMI. Head-end systems may perform a limited amount of data validation before either making the data available for other systems to request or pushing the data out to other systems.
This component operates within the NOC Application Layer, providing the primary interface between data extracted from / sent to the WAN and data used within back-office applications in the NOC layer, e.g., MDM, etc.
Not many clear requirements exist for this element of the AMI. Typically, its properties will be defined by the choice of associated Smart Meters and DCUs deployed within the End-Customer and DCU Application Layers.
However, the choice of Meter Data Management System (MDM) should be independent from the metering system choice, thus interoperability between HES and the MDM, and the use of open standards, is a key factor to consider.
1. Basic Technical Specifications
Interoperability
The HES shall:
● Support IEC 61968-9 to ensure interoperability between different metering systems and a single MDM.
● Offer easy integration with the Utility’s Enterprise Software (e.g., SAP) for functions such as CRM billing, etc.
2. Operational Requirements
2.1 Time-Synchronization
The HES shall:
● Possess an internal clock, synchronized with the AMI’s GPS-based, central timestamp.
2.2 Data Collection
The HES shall:
● Handle the registration of all DCUs (Solution A) or Smart Meters (Solution B) that that connect to its associated WAN.
● Aggregate all metered data received from Smart Meters that connect to its associated NAN and which have registered with the DCU.
● Store all metered data (received from registered Smart Meters) locally (as per §6.6.2.1:C), prior to sending the data to the NOC.
● Facilitate data logging, via direct and secure access (as per §6.6.3 or alternative appropriate means) to locally stored meter data.
2.3 AMI Instructions
The HES shall:
● Be able to forward messages from the MDM to devices in the field (within both the End-Customer and DCU Application Layers).
3. Interface with Wide Area Network (WAN)
3.1 Connectivity
The HES shall:
● Connect to other AMI components within the NOC Application Layer (as defined in this document) across a dedicated LAN or VLAN (i.e., not integrated with the corporate or PSA networks)
● Be equipped with a GSM/GPRS Interface to handle bi-directional communications to/from the WAN Communications Layer.
● Be equipped with a RS-485 interface, furnished with at least 2× RJ45 terminals.
● Configure a data table for interactions with clients in the End-Customer and DCU Application Layers (Solution A) based on the Common Information Model (CIM).
● Be capable of processing complex pricing algorithms, including pre-pay customers, to apportion cost (according to tariff) to metered data profiles received.
● Process the registration of each DCU connecting to the WAN (Solution A)
or
● Process the registration of each MECM connecting to the WAN (Solution B)
3.2 The HES shall manage and monitor the health of communications within its associated WAN.
Head End System Architecture
Picture shows the architecture of Head End System. For more information about architecture please search in our blog.
