Intraday Capacity Access Rules Sample Clauses

Intraday Capacity Access Rules. (General Aspects) These Intraday Capacity Access Rules describe (among other aspects) the requirements that Market Participants must fulfill in order to be able to access and use the available intraday capacities. Article 9 contains a limitation of liability. As a matter of course this liability limitation is in line with all relevant national and European legislation. These Intraday Capacity Access Rules may be amended jointly by the TSOs along the way in order to improve or clarify provisions and procedures and to fill gaps according to Article 13. General grid access for the use of Allocated Capacity is not covered by the scope of the Intraday Capacity Access Rules unless otherwise stipulated in the following provisions. ELES and APG carry out the transmission services in compliance with the legal requirements of grid access in each control area, possible electricity import bans and applicable rules of ELES and APG.
AutoNDA by SimpleDocs

Related to Intraday Capacity Access Rules

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

  • FREQUENCY AND CAPACITY LEVELS No restriction on frequency, capacity and aircraft type

  • Facility Access Notwithstanding any other provision of the Agreement, the Customer shall provide the Authority with such access to the Facility, and such documentation, as the Authority deems necessary to determine the Customer’s compliance with the Customer’s Supplemental Commitments specified in this Schedule B.

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

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Emergency Access Landlord shall have the right to enter the Premises at any time without notice in the event of an emergency.

  • Open Access Same-Time Information System (OASIS): The information system and standards of conduct contained in Part 37 and Part 38 of the Commission’s regulations and all additional requirements implemented by subsequent Commission orders dealing with OASIS.

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

  • Contract Capacity The generation capability designated for the Project shall be the contract capacity in MW designated in the Cover Sheet, net of all auxiliary loads, station electrical uses, and Electrical Losses (the “Contract Capacity”). Throughout the Delivery Term, Seller shall sell and deliver all Product produced by the Project solely to Buyer. In no event shall Buyer be obligated to receive, in any Settlement Interval, any Surplus Delivered Energy. Seller shall not receive payment for any Surplus Delivered Energy. To the extent Seller delivers Surplus Delivered Energy to the Delivery Point in a Settlement Interval in which the Real-Time Price for the applicable PNode is negative, Seller shall pay Buyer an amount equal to the Surplus Delivered Energy (in MWh) during such Settlement Interval, multiplied by the absolute value of the Real-Time Price per MWh for such Settlement Interval.]

  • HIV/AIDS Model Workplace Guidelines Grantee will:

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