Head End System Sample Clauses

Head End System. (HES) The main objective of HES is to acquire meter data automatically avoiding any human intervention and monitor parameters acquired from meters. The AMISP shall provide a HES which is suitable to support the collection and storage of data as per performance level for a defined no. of Smart Meters with facility of future expansion as per the requirement specified in this document. <NOTE: The no of Smart Meters/future expansion may be provided by utility as per their requirement> HES shall be responsible for discovery of all Smart Meters once deployed in the field, the periodic collection of all meter data as well as the processing of all alarms and commands such as connect/disconnect for those meters. HES would perform all the requisite functions as per the defined functionalities of AMI and it is the responsibility of the AMISP to supply the requisite software and hardware to achieve the defined functionalities of AMI. HES shall ensure data integrity checks, for example, checksum, time check, pulse, overflow, etc. on all metered data. HES shall be developed on open platform based on distributed architecture for scalability without degradation of the performance using additional hardware. The scalability shall ensure the ability to handle applicable workloads including the following: <Utility to define the scalability required. An indicative list of parameters is provided below>
Sample 1Sample 2
AutoNDA by SimpleDocs
Head End System. (HES) The main objective of HES is to acquire meter data automatically avoiding any human intervention and monitor parameters acquired from meters. The AMISP shall provide a HES which is suitable to support the collection and storage of data as per performance level for a defined no. of Smart Meters with facility of future expansion as and when required. HES shall be responsible for discovery of all Smart Meters once deployed in the field, the periodic collection of all meter data as well as the processing of all alarms and commands such as connect/disconnect for those meters. HES would perform all the requisite functions as per the defined functionalities of AMI and it is the responsibility of the AMISP to supply the requisite software and hardware to achieve the defined functionalities of AMI. HES shall ensure data integrity checks, for example, checksum, time check, pulse, overflow, etc. on all metered data. HES shall be developed on open platform based on distributed architecture for scalability without degradation of the performance using additional hardware. The scalability shall ensure the ability to handle applicable workloads including the following:
Sample 1Sample 2
Head End System. (HES) The main objective of HES is to acquire meter data automatically avoiding any human intervention and monitor parameters acquired from meters. The bidder shall provide the HES suitable to support the collection and storage of data as per performance level for a defined no. of smart meters with facility of future expansion as per the requirement specified in this document. HES would perform all the requisite functions as per the defined functionalities of AMI and it is the responsibility of the bidder to supply the requisite software and hardware to achieve the defined functionalities of AMI. HES shall ensure data integrity checks, for example, checksum, time check, pulse, overflow, etc. on all metered data. HES shall be developed on open platform based on distributed architecture for scalability without degradation of the performance using additional hardware. HES shall support storage of raw meter data, alarms and alerts for minimum 3 days. 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:
Sample 1

Related to Head End System

  • Interconnection Customer Interconnection Facilities Interconnection Customer shall design, procure, construct, install, own and/or control Interconnection Customer Interconnection Facilities described in Appendix A, Interconnection Facilities, Network Upgrades and Distribution Upgrades, at its sole expense.

  • Interconnection Point The Service Provider is responsible for connecting to the LFC Network at the Interconnection Point. The LFC may only change an Interconnection Point if a change is necessary to protect the security or integrity of that Interconnection Point in order to maintain the continuity of supply of the Wholesale Services. In the event of any such change:

  • Interconnection Points 8.5.1 The IP of a Party (“Receiving Party”) for Measured Internet Traffic delivered to the Receiving Party by the other Party shall be the same as the IP of the Receiving Party for Reciprocal Compensation Traffic under Section 7.1 above.

  • SS7 Network Interconnection 9.7.1 SS7 Network Interconnection is the interconnection of Global Connection local signaling transfer point switches or Global Connection local or tandem switching systems with BellSouth signaling transfer point switches. This interconnection provides connectivity that enables the exchange of SS7 messages among BellSouth switching systems and databases, Global Connection local or tandem switching systems, and other third-party switching systems directly connected to the XxxxXxxxx XX0 network.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Interconnection Product Options Interconnection Customer has selected the following (checked) type of Interconnection Service:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Network Resource Interconnection Service (check if selected)

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