Common use of Head End System Clause in Contracts

Head End System. (HES) a) [5/15] mins interval meter reads b) Other events and statuses coming from meters. The HES shall be cloud enabled and support deployment with high availability clustering and automatic load balancing that ensure hardware as well as application failover. Adequate data base and security features for storage of data at HES need to be ensured. The suggested functions of HES (not exhaustive) may be: a) On power up after installation, Smart Meter shall register itself automatically into the HES along with its metering profile. The HES shall store meter profile status by meter type, hardware & software versions, device IDs, logged in / logged out details etc. b) Upon deployment and establishment of communication, it shall be possible for field level end device nodes (NAN/WAN) like Router/Gateway, Access Point, DCU to have self-discovery and registration. c) Acquisition of meter data on demand & at user selectable periodicity. On demand meter read may be for single meter (unicast) or for a group of meters (multicast). d) Two-way communication with meter/Gateway e) Signals for connect & disconnect of switches present in end points such as meters. This facility shall be provided for both single meter (unicast) as well as for a group of meters (multicast). f) Audit trail and Event & Alarm Logging g) Ability to redirect messages including configuration commands from the MDM in order to reach the desired meter h) Maintain time sync with Gateway / meter i) Store raw data for defined duration (minimum 3 days). HES shall hold the data before it is transferred to the MDM j) Handling of Control signals / event messages on priority k) Manage time distribution to ensure that nodes / meters always have an accurate RTC using NTP servers. The time distribution mechanism shall take into account the network latencies. l) Setting of Smart Meter configurable parameters m) Critical and non-critical event reporting functionality n) Device management functionality to get periodic updates from devices on health check, hardware & firmware version, location mapping etc.

Appears in 2 contracts

Samples: Contract for Appointment of Advanced Metering Infrastructure (Ami) Service Provider, Contract for Appointment of Advanced Metering Infrastructure (Ami) Service Provider

AutoNDA by SimpleDocs

Head End System. (HES) a) Up to [x] numbers of meters installed b) [5/15] mins interval meter reads bc) [y] users requesting data from meters d) Other events and statuses coming from meters. The HES shall be cloud enabled and support deployment with high availability clustering and automatic load balancing that ensure hardware as well as application failover. Adequate data base and security features for storage of data at HES need to be ensured. The suggested functions of HES (not exhaustive) may be: a) On power up after installation, Smart Meter shall register itself automatically into the HES along with its metering profile. The HES shall store meter profile status by meter type, hardware & software versions, device IDs, logged in / logged out details etc. b) Upon deployment and establishment of communication, it shall be possible for field level end device nodes (NAN/WAN) like Router/Gateway, Access Point, DCU to have self-discovery and registration. c) Acquisition of meter data on demand & at user selectable periodicity. On demand meter read may be for single meter (unicast) or for a group of meters (multicast). d) Two-way communication with meter/Gatewaymeter/ DCU e) Signals for connect & disconnect of switches present in end points such as meters. This facility shall be provided for both single meter (unicast) as well as for a group of meters (multicast). f) Audit trail and Event & Alarm Logging g) Ability to redirect messages including configuration commands from the MDM in order to reach the desired meter h) Maintain time sync with Gateway DCU / meter i) Store raw data for defined duration (minimum 3 days). HES shall hold the data before it is transferred to the MDM j) Handling of Control signals / event messages on priority k) Manage time distribution to ensure that nodes / meters always have an accurate RTC using NTP servers. The time distribution mechanism shall take into account the network latencies. l) Setting of Smart Meter configurable parameters m) Critical and non-critical event reporting functionality n) Device management functionality to get periodic updates from devices on health check, hardware & firmware version, location mapping etc.

Appears in 2 contracts

Samples: Appointment of Ami Service Provider for Smart Prepaid Metering, Appointment of Ami Service Provider for Smart Prepaid Metering

AutoNDA by SimpleDocs
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!