Problem Escalation Process. 6.1. If the normal support process does not produce the desired results, or if the severity has changed, the issue may be escalated as follows to a higher level of authority. 6.1.1.1. Severity 1 issues are escalated by Sales or Technical Services to a Supervisor if not resolved within 2 hours; to the Manager level if not resolved within 4 hours; to the Director level if not resolved within the same business day; and to the VP level if not resolved within 24 hours. 6.1.1.2. A customer may escalate an issue by calling 0-000-000-0000, Option 2. Please specify the SalesForce ticket number and the reason why the issue is being escalated. 6.1.1.3. In the event that a customer is not satisfied with the level of support or continual problem with their products, they may escalate a given SalesForce ticket to Manager of Technical Services (0-000-000-0000, Option 2).

Problem Escalation Process. 5.1. If the normal support process does not produce the desired results, or if the severity has changed, the issue may be escalated as follows to a higher level. 5.2. Severity 1 issues are escalated by Sales or Systems Technical Support to a Support Coordinator if not resolved within 4 hours; to the next management level if not resolved within 24 hours. 5.3. A customer may escalate an issue by calling 0-000-000-0000. Please specify the details and Systems Technical Support representative worked with and the reason why the issue is being escalated. 5.4. In the event that a customer is not satisfied with the level of support or continual problem with their products, they may escalate a given issue to the Systems Technical Support Coordinator at 0- 000-000-0000.

Problem Escalation Process. Establish a formal process for escalating problems or issues of any kind including but not limited to poor response times or system interruptions experienced by the Purchaser. Both the Purchaser and Contractor will conduct the following exercise when less than adequate performance has been reported.

Problem Escalation Process. 4.1. The issue enters the Problem Escalation process when it is reported to FMS and recorded in its on-line Support Portal. Client may report the issue directly via the Support Portal, or a member of the Support team may enter the issue into the system on behalf of Client. It is essential that the issue be recorded in the system including adequate detail and steps to reproduce. The issue receives a tracking case number, such as Case 0012345. 4.2. FMS is responsible for reproducing the issue reported in Case 0012345 in their lab. If it is determined to be a defect, the details and any additional information about the issue are recorded and entered into the Engineering Defect Tracking System (DTS). The issue then receives an additional tracking number. 4.3. DTS items are reviewed in a weekly triage meeting made up of members from FMS’s Quality Assurance, Development, Product Management, and Client Services, all of which participate in the triage meeting to assign priority levels. During the meeting, the plan for resolution is discussed and the DTS is categorized according to the following criteria: Customer may track the progress of a particular issue within the Support Portal at any time. Once an issue has been reproduced, assigned a DTS number, and accepted by Engineering, the issue case will be closed. This is intended to reflect that the issue has progressed from the Support queue into the Engineering queue for resolution. Customer may track the progress of the DTS within the Support Portal as it becomes targeted for a particular release, and once it is resolved and available in a release.

Related to Problem Escalation Process

Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.
Escalation Procedure Tentative Rates for those species and products listed in A4a are subject to quarterly escalation in accordance with the following pro- cedures: The calendar quarter index average for each price index described in A5 is the arithmetic average of the three such monthly price indices preceding January 1, April 1, July 1, and October 1. The difference between calendar quarter index average and Base Index listed in A4a shall be the basis for quarterly escalation. To arrive at Current Contract Rates for timber Scaled during the preceding calendar quarter, Tentative Rates for each species shall be reduced or increased by such difference, except when the calendar quarter index average is: (a) Less than the Base Index, the reduction shall not result in a rate below Base Rate or (b) Greater than the Base Index, the increase shall not exceed the difference between Tentative Rate and Base Rate. In the event of Contract Term Extension, the escala- tion procedure will be used during the extension period, except that adjusted payment rates for any calendar quar- ter cannot be less than Tentative Rates, for each species and product group, established under B8.23 for the ex- tension period.
ESCALATION PROCEDURES 48.1 The Standard Practices outlines the escalation process which may be invoked at any point in the Service Ordering, Provisioning, and Maintenance processes to facilitate rapid and timely resolution of disputes.
Evaluation Process ‌ A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory. B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as: 1. Reviewing the employee’s performance; 2. Identifying ways the employee may improve their performance; 3. Updating the employee’s position description, if necessary; 4. Identifying performance goals and expectations for the next appraisal period; and 5. Identifying employee training and development needs. C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file. D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal. E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure. F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.
Review Process A/E's Work Product will be reviewed by County under its applicable technical requirements and procedures, as follows:
Escalation If parties are unable to resolve the issue in a timely manner, as specified above, either Sourcewell or Supplier may escalate the resolution of the issue to a higher level of management. The Supplier will have 30 calendar days to cure an outstanding issue.
Selection Process The Mortgage Loans were selected from among the outstanding one- to four-family mortgage loans in the Seller's portfolio at the related Closing Date as to which the representations and warranties set forth in Subsection 9.02 could be made and such selection was not made in a manner so as to affect adversely the interests of the Purchaser;
Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).
PRICE ESCALATION/DE-ESCALATION (CPI) The County may allow a price escalation provision within this award. The original contract prices shall be firm for an initial one (1) year period. A price escalation/de-escalation will be considered at one (1) year intervals thereafter, provided the Contractor notifies the County, in writing, of the pending price escalation/de-escalation a minimum of sixty (60) days prior to the effective date. Price adjustments shall be based on the latest version of the Consumers Price Index (CPI-U) for All Urban Consumers, All Items, U.S. City Average, non-seasonal, as published by the U.S. Department of Labor, Bureau of Labor Statistics. This information is available at xxx.xxx.xxx. Price adjustment shall be calculated by applying the simple percentage model to the CPI data. This method is defined as subtracting the base period index value (at the time of initial award) from the index value at time of calculation (latest version of the CPI published as of the date of request for price adjustment), divided by the base period index value to identify percentage of change, then multiplying the percentage of change by 100 to identify the percentage change. Formula is as follows: Current Index – Base Index / Base Index = % of Change CPI for current period 232.945 Less CPI for base period 229.815 Equals index point change 3.130 Divided by base period CPI 229.815 Equals 0.0136 Result multiplied by 100 0.0136 x 100 Equals percent change 1.4% % of Change x 100 = Percentage Change CPI-U Calculation Example: A price increase may be requested only at each time interval specified above, using the methodology outlined in this section. To request a price increase, Contractor shall submit a letter stating the percentage amount of the requested increase and adjusted price to the Orange County Procurement Division. The letter shall include the complete calculation utilizing the formula above, and a copy of the CPI-U index table used in the calculation. The maximum allowable increase shall not exceed 4%, unless authorized by the Manager, Procurement Division. All price adjustments must be accepted by the Manager, Procurement Division and shall be memorialized by written amendment to this contract. No retroactive contract price adjustments will be allowed. Should the CPI-U for All Urban Consumers, All Items, U.S City Average, as published by the U.S. Department of Labor, Bureau of Labor Statistics decrease during the term of the contract, or any renewals, the Contractor shall notify the Orange County Procurement Division of price decreases in the method outlined above. If approved, the price adjustment shall become effective on the contract renewal date. If the Contractor fails to pass the decrease on to the County, the County reserves the right to place the Contractor in default, cancel the award, and remove the Contractor from the County Vendor List for a period of time deemed suitable by the County. In the event of this occurrence, the County further reserves the right to utilize any options as stated herein.
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 Escalation Process Sample Clauses

Filter & Search

Related Clauses

Parent Clauses

Sub-Clauses

Related to Problem Escalation Process