PROBLEM SEVERITIES Sample Clauses

PROBLEM SEVERITIES. Problem severities are defined below. It is Cisco’s policy to work with its End User to establish the severity for a problem and to accept the End User’s determination of the severity. Licensor shall accept the severity designation agreed to by Cisco and its End User and communicated to Licensor by Cisco. Licensor’s obligations are as follows: Severity 1 (or “Licensor Severity 1”): An existing network or environment is down or there is a critical impact to an End User’s business operation. Licensor will commit full-time resources around the clock to resolve the situation. Severity 2 (or “Licensor Severity 1”): Operation of customer’s existing network or environment is severely degraded or significant aspects of End User’s business operation are negatively impacted by unacceptable network or environment performance. Licensor will commit full-time resources during Cisco’s Business Hours to resolve the situation. Severity 3 (or “Licensor Severity 2”) : Operational performance of End User’s network or environment is impaired, although most business operations remain functional. Licensor will commit resources during Licensor’s Business Hours to restore service to satisfactory levels. Severity 4 (or “Licensor Severity 3”): Cisco or an End User requires information or assistance on Software capabilities, installation, or configuration. Licensor shall provide response times and resolution times as set forth below: Xxxxxxxxxxxx (Xxxxxxxx Xxxxx 0) - 0 xx Xxxxxx (Severity Level 2) - 4 hrs Serious (Severity Level 3) - 8 hrs Trivial (Severity Level 4) - 24 hrs Catastrophic (Severity Level 1) - 24 hrs Urgent (Severity Level 2) - 48 hrs Serious (Severity Level 3) - 72 hrs Trivial (Severity Level 4) - highest commercially reasonable efforts In the event that the Licensor is unable to meet the time frames set forth for Severity 3 or Severity 4 problems, Licensor shall provide to Cisco, at a minimum, a written plan for addressing the problem within those applicable time frames.
Sample 1
AutoNDA by SimpleDocs

Related to PROBLEM SEVERITIES

  • Problems To endeavour to resolve in a fair and just manner any problems, grievances or difficulties which may be encountered while you volunteer with us;

  • Problem Solving Employees and supervisors are encouraged to attempt to resolve on an informal basis, at the earliest opportunity, a problem that could lead to a grievance. If the matter is not resolved by informal discussion, or a problem-solving meeting does not occur, it may be settled in accordance with the grievance procedure. Unless mutually agreed between the Employer and the Union problem-solving discussions shall not extend the deadlines for filing a grievance. The Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, either with the employee or alone, shall present to the appropriate supervisor a written request for a meeting. If the supervisor agrees to a problem- solving meeting, this meeting shall be held within fourteen (14) calendar days of receipt of the request. The supervisor, employee, Union Xxxxxxx, and up to one (1) other management person shall attempt to resolve the problem through direct and forthright communication. If another member of management is present that person will not be hearing the grievance at Step Two, should it progress to that Step. The employee, the Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, may participate in problem-solving activities on paid time, in accordance with Article 31, Union Rights, Section 1H.

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

  • Technical Objections to Grievances It is the intent of both Parties of this Agreement that no grievance shall be defeated merely because of a technical error, other than time limitations in processing the grievance through the grievance procedure. To this end, an arbitration board shall have the power to allow all necessary amendments to the grievance and the power to waive formal procedural irregularities in the processing of a grievance, in order to determine the real matter in dispute and to render a decision according to equitable principles and the justice of the case.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

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

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

  • MANAGEMENT GRIEVANCES 14.01 It is understood that the Management may bring forward at any meeting held with the Union Representative any complaint with respect to the conduct of the Union, or Stewards, and that if such complaint by Management is not settled to the mutual satisfaction of the conferring Parties, it may be treated as a grievance and referred to arbitration in the same way as the grievance of any employee.

  • Management Grievance The Employer may initiate a grievance at Step 3 of the grievance procedure by the Employer or designate presenting the grievance to the President of the Union or designate. Time limits and process are identical to a union grievance.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

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