Security initiatives regarding Smart Metering Sample Clauses

Security initiatives regarding Smart Metering. In general terms, there are many countries with AMI systems under development and/or deployment. There are also many variants in the topology and specifications of the system, although most solutions are based on the existence of a kind of Head End System (HES), which is in charge of managing all the metering information retrieved from smart meters, as well as personal, billing and security information. This element is also the source of any kind of commands to be delivered to meters, e.g. connection/disconnection of the subscriber to/from the network, change of settings, other commands and firmware upgrades. This HES is linked with meters through one or more intermediate devices, which provide connectivity and eventual adaptation of communication protocols to the metering protocols which implement final communication with the meters. These intermediate devices can be the boundary of segments with different physical transmission media, and therefore different protocol specifications. Examples of countries that already have ongoing AMI initiatives are UK (with plans to end deployment by 2020), France (with end of deployment expected by 2020, with about 35 million devices), Portugal, Spain (with expected end of deployment in 2019), The Netherlands, Germany, Italy (with the world’s major smart meter deployment, about 30 million devices), Denmark, Sweden, Norway, the British Columbia and Ontario in Canada, several states of the US like California, Texas, Florida, Maryland, the State of Victoria in Australia, Iran, Lebanon, Saudi Arabia and Japan. Cybersecurity is a common concern for all these deployments, which is usually implemented at application level (for both the smart meter and HES communication segments, taking advantage of currently operative communication technologies and protocols).
Sample 1
AutoNDA by SimpleDocs

Related to Security initiatives regarding Smart Metering

  • 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.

  • 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:

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Information regarding Interconnection Facilities 4.2.1 The SPD shall be required to obtain all information from the STU/CTU/concerned authority with regard to the Interconnection Facilities as is reasonably necessary to enable it to design, install and operate all interconnection plant and apparatus on the SPD’s side of the Delivery Point to enable delivery of electricity at the Delivery Point. The transmission of power up to the point of interconnection where the metering is done for energy accounting shall be the responsibility of the SPD at his own cost.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Equipment and Software Requirements In order to view and retain electronic communications that we make available to you, you must have: • A PC or other device with an Internet browser that has “cookies” enabled and supports 128 bit encryption • An Internet connection • An email address • A PDF viewer (such as Adobe Reader) • A printer or computer with sufficient electronic storage space All communications shall be delivered to the last address we have on file for you. These notices will be sent through electronic delivery (email) and will be considered delivered the same day as sent. If you have opted out of electronic delivery, communications sent to you through the United States Postal Service are considered delivered 5 business days after the postmark date. It is your responsibility to notify the Custodian of any email address change or residential address change. We will not be held liable for any losses or damages if you have not provided Custodian with the most current address information. The electronically signed copy of this document should be considered equivalent to a printed hard copy form. It is considered a true and complete record of the document, admissible in arbitration and/or administrative hearings or proceedings. Your electronic signature on the Application and other electronic forms such as the Investment Direction are considered valid and the same as if the paper form or Application were signed.

  • Commencement of Interconnection Activities If the Developer executes the final LGIA, the ISO, Connecting Transmission Owner and the Developer shall perform their respective obligations in accordance with the terms of the LGIA, subject to modification by FERC. Upon submission of an unexecuted LGIA in accordance with Section 30.11.3, the Parties shall promptly comply with the unexecuted LGIA, subject to modification by FERC.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

Time is Money Join Law Insider Premium to draft better contracts faster.