R equired Notice of Maintenance Sample Clauses

R equired Notice of Maintenance. Unless as otherwise agreed to by Subscriber on a case-by-case basis, Service Provider shall provide no less than thirty (30) calendar day’s prior written notice to Subscriber of all non-emergency maintenance to be performed on the Services, such written notice including a detailed description of all maintenance to be performed. For emergency maintenance, Service Provider shall provide as much prior notice as commercially practicable to Subscriber and shall provide a detailed description of all maintenance performed no greater than one (1) calendar day following the implementation of the emergency maintenance.
AutoNDA by SimpleDocs

Related to R equired Notice of Maintenance

  • Required Notice The Company will advise the appropriate committee or committees as soon as possible, and in any case not less than one hundred and eighty (180) days before the introduction thereof, of mechanization, technological changes and/or automation which the Company has decided to introduce and which will result in terminations or other significant changes in the employment status of employees. The Company will advise the appropriate committee or committees as soon as possible, and in any case not less than thirty (30) days before the expected date of the change of the anticipated time sequence of final installation and production start-up and the anticipated effect on the job status of individual employees.

  • Required Notices The Board of Directors of the Company shall not take any of the actions referred to in Section 6.03(b) unless the Company shall have delivered to Parent a prior written notice advising Parent that it intends to take such action, and, after taking such action, the Company shall, if such action is in connection with a Company Acquisition Proposal, continue to advise Parent on a current basis of the status and terms of any discussions and negotiations with the Third Party. In addition, the Company shall notify Parent promptly (but in no event later than 24 hours) after receipt by the Company (or any of its Representatives) of any Company Acquisition Proposal, any written indication from a Third Party that such Third Party is considering making a Company Acquisition Proposal or any written request for information relating to the Company or any of its Subsidiaries or for access to the business, properties, assets, books or records of the Company or any of its Subsidiaries by any Third Party that has indicated that it is considering making, or has made, a Company Acquisition Proposal. The Company shall within 24 hours of receipt thereof provide such notice orally and in writing and shall identify the Third Party making, and the material terms and conditions of, any such Company Acquisition Proposal, indication or request, and shall promptly (but in no event later than 24 hours after receipt) provide to Parent copies of all material correspondence and written materials sent or provided to the Company or any of its Subsidiaries that describes any terms or conditions of any Company Acquisition Proposal. The Company shall keep Parent reasonably informed, on a reasonably current basis, of the status and details of any such Company Acquisition Proposal, indication or request. Any material amendment to any Company Acquisition Proposal will be deemed to be a new Company Acquisition Proposal for purposes of the Company’s compliance with this Section 6.03(c).

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Final Notice of Non-Compliant Work The Final Notice of Non-Compliant Work issued as a result of the Inspection for Material Completion, also known as the Final Punch List. Upon the completion or correction of this Non- Compliant Work (“punch list” work) the Design Professional will issue the Final Certificate.

  • Required Acceptance of Daily Load Deliveries and Notification If the State is harmed by purchaser’s refusal to accept up to 10 truck deliveries of any one sort per day, Purchaser will be in breach of contract and subject to damages as per the D-026.2 and D-027.2 clauses. A truck delivery is all the wood delivered including sorts on super trucks, mule trains and pups brought to the delivery point by a single truck. The Purchaser shall notify the Contract Administrator at least 48 hours in advance if:

  • ACCEPTANCE OF MATERIAL 12.1 All components used in the manufacture or construction of materials, supplies and equipment, and all finished materials, shall be new, the latest make/model, of the best quality, and the highest grade workmanship.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Renewal Notice; Notification of Changes Subject to governing law, XOOM can renew this Agreement with new or revised Terms. XOOM will send you written notice at least (30) days before the end of the Term. The notice will specify the date by which you must advise XOOM if you do not want to renew your Agreement. If you do not advise XOOM by the specified date, this Agreement will automatically renew at the fixed rate or variable rate then in effect in accordance with the notice. XOOM reserves the right, with fifteen (15) days’ notice, to amend this Agreement to adjust its service to accommodate any change in regulations, law, tariff or other change in procedure required by any third party that may affect XOOM’s ability to continue to serve you under this Agreement.

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Response/Compliance with Audit or Inspection Findings A. Grantee must act to ensure its and its Subcontractors’ compliance with all corrections necessary to address any finding of noncompliance with any law, regulation, audit requirement, or generally accepted accounting principle, or any other deficiency identified in any audit, review, or inspection of the Contract and the services and Deliverables provided. Any such correction will be at Grantee’s or its Subcontractor's sole expense. Whether Xxxxxxx's action corrects the noncompliance shall be solely the decision of the System Agency.

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