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 escalation 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

  • Building Commissioning Services The Owner may provide as a part of its testing services the Building Commissioning services involving the project’s HVAC and exhaust systems, temperature control systems, fire detection and alarm systems, emergency power and lighting system, fire suppression system, security locks and security locking control systems, food service equipment (if applicable), and laundry equipment (if applicable). In the event the Using Agency’s Program specifies additional commissioning services, the Owner shall procure such services as well. The Owner, through its Executive Administrator, may engage an independent Commissioning Authority. It is the intent of this Article that the Commissioning Authority enforce the requirements mentioned herein and certify that the systems and equipment listed all function properly prior to the initiation of each final inspection.

  • Vehicle Base Specifications Note: The actual vehicle awarded may exceed the minimum specifications stated below. The Authorized User may elect to add additional Options, delete Options, or substitute a vehicle feature that is an Option with another Option. See Contract Section III.6

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

  • Revenue Metering The Connecting Transmission Owner’s revenue metering will be located on the generator side of the 115kV breaker at the Xxxxx Solar Collector Substation and will consist of: • three (3) combination current/voltage transformer (“CT/VT”) units (manufacturer and model ABB/Xxxxxxx KXM-550, GE Grid Solutions KOTEF 000.XX, or other equivalent specified by Connecting Transmission Owner); and • one (1) revenue meter. The ratios of the CTs and VTs will be provided by Connecting Transmission Owner upon its review of the Interconnection Customer’s design documents. (Note: Connecting Transmission Owner’s revenue metering CTs and VTs cannot be used to feed the Interconnection Customer’s check meter.) SERVICE AGREEMENT NO. 2556

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

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

  • TECHNICAL TASKS Products that require a draft version are indicated by marking “(draft and final)” after the product name in the “Products” section of the task/subtask. If “(draft and final)” does not appear after the product name, only a final version of the product is required. Subtask 1.1 (Products) describes the procedure for submitting products to the CAM.

  • Additional RO Review Criteria (1) In addition to the requirements in Subparagraph 34A, the RO must:

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