Functional escalation Sample Clauses

Functional escalation. Horizontal, functional escalation involves referring unresolved queries to a team with greater expertise or more extensive rights or access levels. If the ITS Service Desk cannot resolve a query as part of first level support, the functional escalation process will be initiated. Incidents shall be referred to the next level in the escalation process, i.e. either the Corporate Communications web team or ITS User Services. Any query that cannot be resolved by either of these shall be referred to ITS Software Services. If it is not possible to find a solution within ETH, ITS User Services shall open a ticket with Adobe. Hierarchical, or vertical escalation means that a higher level of management is consulted or notified. This may be necessary for incidents involving high levels of damage where the service is significantly restricted or there is disagreement as to the level of service provision. Under the hierarchical escalation procedure, incidents shall be escalated as follows: • Staff on the Corporate Communications web team • Head of Corporate Communications • Executive Board
AutoNDA by SimpleDocs
Functional escalation. If the Assigned Support Agent determines that resolution of the case will require services not covered by a Support Services Agreement, then he/she will escalate the case to the appropriate functional group within ESC. A case may be escalated to: a) ESC’s Projects Group if the case involves project work covered under a separate agreement; or b) ESC’s sales group if resolution requires services that are not covered under an existing agreement. To escalate a case, the Assigned Support Agent will discuss the case with the appropriate functional group, contact the User to inform him/her that the case is being escalated, send the User a confirming email, and close the case record. The functional group assuming responsibility for the case will contact the User and proceed to work with him/her to resolve the issue under the terms of an appropriate agreement.
Functional escalation. Functional escalation is the normal transfer of an incident to individuals or teams with a higher level of technical knowledge to reach a resolution. Many incidents will be escalated internally in this manner. Standard process is to escalate through 1st, 2nd and 3rd line teams until the fault is rectified, but the nature of the problem may allow for the bypass some of these stages. As the incident moves through this process, the support ticket will be updated at appropriate stages.

Related to Functional escalation

  • Non-Escalation Unless otherwise specified within the RFP documents, the unit prices reflected on the contract shall remain firm with no provision for price increases during the term of the contract.

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

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

  • Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.

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

  • Preconstruction Conference Prior to, or concurrent with, the issuance of the Notice to Proceed with Construction, a conference will be convened for attendance by the Owner, Contractor, A/E and appropriate Subcontractors. The purpose of the conference is to establish a working understanding among the parties as to the Work, the operational conditions at the Project Site, and general administration of the Project. Topics include communications, schedules, procedures for handling Shop Drawings and other submittals, processing Applications for Payment, maintaining required records and all other matters of importance to the administration of the Project and effective communications between the project team members.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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

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