Call/Incident Solution Sample Clauses

Call/Incident Solution. This step should be followed when the SDO judges that the call/incident solution is reached. In this case, the SDO should:  Ensure that all actions within this call are closed;  Update the call details in the SMT tool with the call/incident solution;  Send the solution e-mail to the call issuer;  Update the call status to “Resolved”. More information, including the flowchart outlining these tasks involved in the “Call/Incident Management Closure” is available in section E.4. Appendix A. Services for the Customs Trans-European Systems (TES) – SLA Applicability This annex details the Customs TES for which the Service Desk operations are managed by the current SLA. National Administrations Customs TES Responsible Parties - Participating National Administrations Start date & Duration NCTS Service Desk All MSA - On-going - Duration defined by TOC - Andorra - Iceland - Norway - San Marino - Serbia - Switzerland - The former Yugoslav Republic of Macedonia - Turkey - On-going - Duration defined by TOC Other participating NA No National Service Desk ECS Service Desk All MSA - On-going - Duration defined by TOC ICS Service Desk All MSA - On-going - Duration defined by TOC EOS Service Desk All MSA - On-going - Duration defined by TOC COPIS Service Desk All MSA - On-going - Duration defined by TOC UUM&DS Service Desk All MSA - From 02/10/2017 - Duration defined by TOC Customs Decisions Service Desk All MSA - From Q4 2017 - Duration defined by TOC XXX Service Desk All MSA - From 01/01/2017 - Duration defined by TOC - Norway - Switzerland - Turkey - From 01/01/2017 - Duration defined by TOC Table 13: Services for the Customs TES – National Administrations EUROPEAN COMMISSION – DG TAXUD Customs TES Responsible Party Start date and Period All Customs TES DG TAXUD (ITSM Service Desk) - On-going10 - Duration defined by TOC Table 14: Services for the Customs TES – DG TAXUD 10 Start Date to be determined for XXX, Customs Decisions and UUM&DS system. DG TAXUD REF.: ITSM2_LOT2-SC02-QTM- 33-SLA-ECUST-SD SLA for the Service Desks of the Customs TES between the National Administrations and DG TAXUD VERSION: 2.90-EN WORKING HOURS OF THE SERVICE DESKS□ ISSUE DATE: 03/11/2017 Appendix B. Working Hours of the Service Desks This appendix defines the hours during which the Service Desks can be reached via phone, in the various countries operating a NSD for one or more Customs trans-European system(s). It is recommended that the NSD maintains a rotation system as far as the total ser...
AutoNDA by SimpleDocs

Related to Call/Incident Solution

  • Data Incidents Merchant must report all instances of a Data Incident (as defined in the American Express Merchant Operating Guide) immediately to ISO after discovery of the incident. Merchant must ensure data quality and that Transaction Data and customer information is processed promptly, accurately, and completely, and complies with the American Express Technical Specifications. THE FOLLOWING SERVICES ARE PROVIDED BY ISO ONLY. Bank shall not have any obligation or liability of any nature in connection with such services. PART THREE

  • Reporting Unsuccessful Security Incidents Business Associate shall provide Covered Entity upon written request a Report that: (a) identifies the categories of Unsuccessful Security Incidents; (b) indicates whether Business Associate believes its current defensive security measures are adequate to address all Unsuccessful Security Incidents, given the scope and nature of such attempts; and (c) if the security measures are not adequate, the measures Business Associate will implement to address the security inadequacies.

  • Security Incident Notification The Transfer Agent shall promptly notify the Trust but in no event later than 72 hours following discovery of any Security Incident(s). Such notification shall include the extent and nature of such intrusion, disclosure, or unauthorized access, the identity of the compromised Customer Confidential Information (to the extent it can be ascertained), how the Transfer Agent was affected by the Security Incident, and its response to such Security Incident. The Transfer Agent shall use continuous and diligent efforts to remedy the cause and the effects of such Security Incident in an expeditious manner and deliver to the Trust a root cause analysis and future incident Mitigation plan with regard to any such incident. The Transfer Agent shall reasonably cooperate with the Trust’s investigation and response to each Security Incident. If the Trust determines in its sole discretion that it may need or be required to notify any individual(s) as a result of a Security Incident, the Trust shall have the right to control all such notifications and the Transfer Agent shall bear all direct costs associated with the notification, to the extent the notification and corresponding actions are required by U.S. law, and subject to the limitation of liability set forth in the Agreement. Without limiting the foregoing, unless otherwise required by U.S. law, no such notifications shall be made by the Transfer Agent without the Trust’s prior written consent and the Trust shall, together with the Transfer Agent, determine the content and delivery of all such notifications. For the avoidance of doubt, the Transfer Agent shall be solely responsible for all costs and expenses, subject to the limitations of liability under the Agreement that the Trust and/or the Transfer Agent may incur to the extent that they are attributable to or arise from the Transfer Agent’s breach of its confidentiality obligations under the Agreement.

  • Reporting Security Incidents The Business Associate will report to the County any Incident of which the Business Associate becomes aware that is:

  • Shift Change Where employees are assigned mid-week to work a non-day shift (whether due to emergencies or a shift change) and as a result lose a shift in the regular work week, such employees will be paid six (6) hours for such loss of earnings.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Layoff Recall Section 1. Bargaining unit employees shall be laid off and recalled on the basis of available work within each job classification. Layoffs shall be in reverse order of seniority and recalls shall be in order of seniority; provided however, that in order to avoid layoff and in order to be subject to recall, the most senior employee within the affected classification must be qualified, in the judgment of the University, to perform all available work. Any gross abuse of the University's discretion to judge qualifications shall be subject to the grievance procedure. Any employee who would otherwise be laid off may bump (i.e., replace) the least senior employee in another bargaining unit job classification if they previously held such job with the University and remain qualified, in the judgment of the University, to perform all work available in the job into which they are bumping. An employee who elects not to bump shall not lose their right to recall to the employee’s regular job, but shall lose their bumping rights for the duration of the layoff. When it becomes necessary to lay off an employee, such employee shall, if possible, be notified at least ten (10) work days before the layoff occurs; provided, however, such notice shall not be required with respect to temporary layoffs or lack of work occasioned by breakdown of machinery, floods, fires, utility failures, Acts of God, or other causes beyond the University's control. When an employee is to be recalled from layoff, the University shall notify the employee by telephone (confirmed by certified or hand delivered letter, copy to Chief Xxxxxxx) specifying the time to report back to work, which notice shall, if possible, not be less than five (5) work days prior to the reporting time. In order to be eligible for recall, any employee who is laid off must keep the University currently advised in writing of their current whereabouts, address and telephone number, and any temporary changes thereof. The employee shall, within twenty-four (24) hours after receiving notice of recall, notify the University if for any reason the employee cannot report for work at the specified time. In the event an employee is unable to return to work due to illness or injury certified by a physician, the employee shall not lose their right to subsequent recall but the University may pass them over in order to fill an available position.

  • Resolving an Employment Relationship Problem The employee and employer should first make a reasonable effort to discuss the problem and settle it by mutual agreement. (If it’s a personal grievance, it must first be raised with the employer within 90 days - Personal Grievances are explained further below). An employee (or employer) has the right to be represented at any stage. When a problem arises, union members should contact their local NZEI Te Riu Roa field officer for advice and representation. Employers should contact NZSTA or other adviser/representative of choice.

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

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