Level 1 Breakdown Sample Clauses

Level 1 Breakdown. In the event of a level 1 breakdown, individual users shall be affected. The service as a whole shall not be affected. The breakdown shall be processed and updated within the support hours.
AutoNDA by SimpleDocs

Related to Level 1 Breakdown

  • Breakdown The failure of a COVERED PART under normal service and usage of the VEHICLE. A COVERED PART has failed when it can no longer perform the function for which it was designed solely because of its condition.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Downtime There may be downtime during the Migration. The duration of the downtime will depend on the amount of data that Agency is migrating. Axon will work with Agency to minimize any downtime. Any VIEVU mobile application will need to be disabled upon Migration.

  • Tie Breaker The parties agree to utilize the following procedure if two or more members of the bargaining unit hold the same position within the same department and have the identical seniority dates: 1. If two or more bargaining unit members have the same amount of time in a particular classification, the first tiebreaker is the date of continuous University service. Continuous service is that service unbroken by a resignation or termination from the University. 2. In the event that a tie is not broken by the foregoing procedure, the second tiebreaker shall be the uninterrupted service of an employee with a state agency, a county office, or a state-supported college or university where no break in service occurs. 3. In the event a tie is not broken by either of the foregoing procedures, we will use the last four (4) digits of the Social Security Number, in ascending order with the lowest number prevailing (i.e. 0001, 0002, 0003, 0004 – 0001 Prevails).

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

  • Inclement Weather 24.1 This Inclement Weather clause sets out the full rights, obligations and entitlements of the parties and establishes the conditions under which payment for periods of inclement weather shall be made. 24.2 This Inclement Weather clause is to be read and observed in lieu of the provisions of the award and VBIA. 24.3 Definition – inclement weather Inclement weather shall mean the existence of rain or abnormal climatic conditions (whether they be those of hail, snow, cold, high wind, severe dust storm, extreme high temperature or the like or any combination thereof) by virtue of which it is either not reasonable or not safe for employees exposed thereto to continue working whilst the same prevail.

  • Vulnerability Management BNY Mellon will maintain a documented process to identify and remediate security vulnerabilities affecting its systems used to provide the services. BNY Mellon will classify security vulnerabilities using industry recognized standards and conduct continuous monitoring and testing of its networks, hardware and software including regular penetration testing and ethical hack assessments. BNY Mellon will remediate identified security vulnerabilities in accordance with its process.

  • Equipment Failures In the event of equipment failures beyond the Administrator's control, the Administrator shall take reasonable and prompt steps to minimize service interruptions but shall have no liability with respect thereto. The Administrator shall develop and maintain a plan for recovery from equipment failures which may include contractual arrangements with appropriate parties making reasonable provision for emergency use of electronic data processing equipment to the extent appropriate equipment is available.

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