Voltage Control Sample Clauses

Voltage Control. Voltage Control is the joint responsibility of the two NCCs and shall be carried out in close mutual liaison.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Voltage Control. Project Developer shall cooperate with Consumers to regulate the voltage level at the Point of Delivery by controlling its generators in accordance with Consumers' instructions. Such instructions shall include, but not be limited to, (a) maintaining voltage or (b) delivering real and reactive power to the Point of Delivery at levels specified by Consumers. The instructions given by Consumers shall be consistent with the normal practices adhered to by Consumers with respect to its own generators located on its system.
Sample 1Sample 2
Voltage Control. The ISO and NEVP shall coordinate the use of voltage control equipment to maintain transmission voltages and reactive flows at mutually agreed upon levels to ensure system stability within the operating range of electrical equipment and in accordance with WSCC MORC. The ISO and NEVP shall operate the facilities at the Interconnection at reactive reserve margins that are adequate to maintain minimum acceptable voltage limits under facility Outage conditions. Agreed upon voltage schedule limits and reactive flows are specified in Service Schedule 7.
Sample 1Sample 2
Voltage Control. This control mode will work similarly to P(f) Control for the active power. In this case the variable to be controlled is the voltage at the point of connection of the hybrid plant to the electrical power grid. The operator will fix a voltage set point that works in a closed-loop voltage control system.
Sample 1
Voltage Control. [Section 3.2.5] • Mohave - Laughlin 500 kV Intertie NEVP shall be responsible for supplying the VAR requirements of Laughlin Substation 69 kV load and the 500/69 kV transformers. At the Point of Interconnection, NEVP is committed to help maintain acceptable voltage. It is recognized that the Mohave 500 kV voltage is affected by several factors and cannot be solely controlled by NEVP. Under normal conditions, Mohave 500 kV voltage should be kept within the following limits: Voltage range: 525 – 535 kV Target Voltage 530 – 535 kV Associated with these voltages, the following targets apply to MVAR flow at the Interconnection: MVAR Schedule: 0 MVAR MVAR Limit: +20 to –20 MVAR • Merchant 230 kV Intertie At the Point of Interconnection, NEVP is committed to help maintain acceptable voltage. It is recognized that the Eldorado 230 kV voltage is affected by several factors and cannot be solely controlled by NEVP. Under normal conditions, Eldorado 230 kV voltage should be kept within the following limits: Voltage range: 230 – 242 kV Target Voltage 236 – 238 kV Associated with these voltages, the following targets apply to MVAR flow at the Interconnection: MVAR Schedule: 0 MVAR MVAR Limit: +80 to –80 MVAR SERVICE SCHEDULE 8 INFORMATION EXCHANGE PROCEDURES FOR GRID OPERATIONS [Section 3.2.6] Information Exchange The ISO and NEVP shall coordinate the exchange of any information specified in Section 3.2.6 concerning the Interconnection facilities and the status of the control areas that may affect the operation of the Interconnection or either of the interconnected control areas. Real time information shall be communicated in the most efficient method possible through any shared electronic, voice, or facsimile. Service Schedule 9 lists information necessary for the reliable operation of the ISO, NEVP, and the WSCC. SERVICE SCHEDULE 9 INTERCONNECTION INFORMATION [Section 3.2.6.1] Information necessary for the reliable operation of the ISO, NEVP, and the WSCC shall include, but not be limited to, the following operational data:
Sample 1
Voltage Control. Applicant shall cooperate with Utility to regulate the voltage level at the Point of Delivery by controlling its generators in accordance with Utility instructions. Such instructions shall include, but not be limited to, (a) maintaining voltage or (b) delivering real and reactive power to the Point of Delivery at levels specified by Utility. The instructions given by Utility shall be consistent with the normal practices adhered to by Utility with respect to its own generators located on its system.
Sample 1
Voltage Control. Voltage control is a control function controlling the voltage at the Interconnection Boundary measured at the Point of Delivery. If the voltage set point is to be changed, such change shall be commenced within 2 seconds and completed no later than 30 seconds after receipt of an order to change the set point unless otherwise agreed with CEB. The controlled voltage shall not deviate from the set point by more than ±0.5% of the nominal voltage. The control droop, defined as the voltage change (per unit) caused by a change in reactive power (per unit), shall be set accordingly. When the voltage control has reached the Facility’s design limits, the control function shall await possible overall control from the transformer on load tap changer or other voltage control functions.
Sample 1
AutoNDA by SimpleDocs
Voltage Control. The ISO and CFE shall coordinate the use of voltage control equipment to maintain transmission voltages and reactive flows at mutually agreed upon levels to ensure system stability within the operating range of electrical equipment and in accordance with WSCC MORC. The ISO and CFE shall operate the facilities at the Interconnection at reactive reserve margins that are adequate to maintain minimum acceptable voltage limits under facility Outage conditions. Agreed upon voltage schedule limits and reactive flows will be specified in Service Schedule 7.
Sample 1

Related to Voltage Control

  • Access Control Supplier will maintain an appropriate access control policy that is designed to restrict access to Accenture Data and Supplier assets to authorized Personnel. Supplier will require that all accounts have complex passwords that contain letters, numbers, and special characters, be changed at least every 90 days, and have a minimum length of 8 characters.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage. Measures: • As part of the SAP Security Policy, Personal Data requires at least the same protection level as “confidential” information according to the SAP Information Classification standard. • Access to Personal Data is granted on a need-to-know basis. Personnel have access to the information that they require in order to fulfill their duty. SAP uses authorization concepts that document grant processes and assigned roles per account (user ID). All Customer Data is protected in accordance with the SAP Security Policy. • All production servers are operated in the Data Centers or in secure server rooms. Security measures that protect applications processing Personal Data are regularly checked. To this end, SAP conducts internal and external security checks and penetration tests on its IT systems. • SAP does not allow the installation of software that has not been approved by SAP. • An SAP security standard governs how data and data carriers are deleted or destroyed once they are no longer required.

  • Input Control The possibility to subsequently verify and determine whether, and by whom, personal data was entered into, changed or removed from data processing systems must be ensured. • Definition of entry authorisation • Logging of logins

  • Physical Access Control Unauthorized persons are prevented from gaining physical access to premises, buildings or rooms where data processing systems that process and/or use Personal Data are located.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”).

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