Header Extension Object and Custom Header Objects
Header Extension Object and Custom Header Objects Sample Clauses
Related to Header Extension Object and Custom Header Objects
Interconnection Customer Compensation for Actions During Emergency Condition The CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff for its provision of real and reactive power and other Emergency Condition services that the Interconnection Customer provides to support the CAISO Controlled Grid during an Emergency Condition in accordance with Article 11.6.
Technical Objections No grievance shall be defeated merely because of a technical error, other than time limitations in the processing of the grievance through the grievance procedure. To this end, an arbitrator shall have the power to waive formal procedural irregularities in the processing of the grievance in order to determine the real matter in dispute.
Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.
Response to Objections Each Party retains the right to respond to any objection raised by a Participating Class Member, including the right to file responsive documents in Court no later than five court days prior to the Final Approval Hearing, or as otherwise ordered or accepted by the Court.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
Addressing Objections Raised During Public Comment Period The Parties agree that the procedure contemplated for public review of this Stipulated Order and the Regional Water Board’s or its delegate’s adoption of this Stipulated Order is lawful and adequate. The Parties understand that the Regional Water Board or its delegate has the authority to require a public hearing on this Stipulated Order. If procedural objections are raised or the Regional Water Board requires a public hearing prior to the Stipulated Order becoming effective, the Parties agree to meet and confer concerning any such objections, and may agree to revise or adjust the procedure and/or this Stipulated Order as necessary or advisable under the circumstances.
Trunk Forecasting Requirements 14.2.1 Initial trunk forecast requirements. At least ninety (90) days before initiating interconnection in a LATA, Alltel shall provide Verizon a two (2)-year traffic forecast that complies with the Verizon Interconnection Trunking Forecast Guide, as revised from time to time. This initial traffic forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Interconnection Trunk groups in the LATA over the next eight (8) quarters.
Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.
361 Acceptance of Specified Roads Specified Road work may be accepted subject to completion of clearing work that does not affect the road structure when completion is delayed for reasons beyond control of Purchaser, such as adverse weather. Specified Road work may be accepted subject to completion of planting and seeding for soil stabilization when completion is delayed for reasons beyond control of Purchaser, such as seasonal limitations. Purchaser shall complete planting or seeding on such road during the next suitable planting season. Specified Road work may be conditionally accepted prior to the application of dust palliatives when application is not necessary to prevent dusting of the road surface due to climatic conditions. Purchaser shall apply dust palliative on such roads prior to use during periods when dusting may occur. Prior to request for final inspection, Specified Road work, roadways, borrow pits, and quarries, occupied and no longer needed by Purchaser in connection with Purchaser’s Operations, shall be cleared of all rubbish, excess materials, and temporary structures.
Objections to New Subprocessors (a) If Customer has a legitimate reason under Data Protection Law to object to the new Subprocessors’ processing of Personal Data, Customer may terminate the Agreement (limited to the Cloud Service for which the new Subprocessor is intended to be used) on written notice to SAP. Such termination shall take effect at the time determined by the Customer which shall be no later than thirty days from the date of SAP’s notice to Customer informing Customer of the new Subprocessor. If Customer does not terminate within this thirty day period, Customer is deemed to have accepted the new Subprocessor.
