Costs of Compliance with Emergency Operating Principles and Procedures Clause Samples

The 'Costs of Compliance with Emergency Operating Principles and Procedures' clause defines which party is responsible for expenses incurred when following emergency protocols or procedures. In practice, this clause typically outlines whether the costs of implementing emergency measures—such as additional staffing, equipment, or operational changes—are borne by the service provider, the client, or shared between them. Its core function is to allocate financial responsibility for emergency compliance, ensuring that both parties understand their obligations and reducing disputes over unexpected costs during emergency situations.
Costs of Compliance with Emergency Operating Principles and Procedures. In accordance with each Party’s OATT, or other applicable agreements, each Party is to bear its own costs of compliance with this Article. Purchases of emergency energy by PJM under this Article in order to address the flow ofDEP, or purchases of emergency energy by DEP under this Article in order to address the flow of PJM, shall occur in accordance with this Agreement.
View SourceView Similar (10)

Related to Costs of Compliance with Emergency Operating Principles and Procedures

  • COMPLIANCE WITH POLICIES AND PROCEDURES During the period that Executive is employed with the Company hereunder, Executive shall adhere to the policies and standards of professionalism set forth in the Company’s Policies and Procedures as they may exist from time to time.

  • Safeguarding requirements and procedures (1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls: (i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems). (ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute. (iii) Verify and control/limit connections to and use of external information systems. (iv) Control information posted or processed on publicly accessible information systems. (v) Identify information system users, processes acting on behalf of users, or devices. (vi) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems. (vii) Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse. (viii) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals. (ix) Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices. (x) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems. (xi) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. (xii) Identify, report, and correct information and information system flaws in a timely manner. (xiii) Provide protection from malicious code at appropriate locations within organizational information systems. (xiv) Update malicious code protection mechanisms when new releases are available. (xv) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.

  • COMPLIANCE WITH GOVERNMENTAL RULES AND REGULATIONS; RECORDS The Trust assumes full responsibility for its compliance with all securities, tax, commodities and other laws, rules and regulations applicable to it.

  • Compliance with Consensus Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/general/consensus-­‐policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”).

  • COMPLIANCE WITH NEW YORK STATE INFORMATION SECURITY BREACH AND NOTIFICATION ACT Contractor shall comply with the provisions of the New York State Information Security Breach and Notification Act (General Business Law Section 899-aa; State Technology Law Section 208).