INCIDENT PRIORITISATION Sample Clauses

INCIDENT PRIORITISATION. Client shall promptly, following discovery, notify Supplier of any Error via the Helpdesk and provide Supplier with reasonable detail of the nature and circumstances of the Error. Each Party shall categorise Errors as follows: 4.1. Urgent (P1) Priority Support Service Incidents means incidents that prevent the use of the Subscription Services including but not limited to an inability to log-in and critical loss of Data; 4.2. High (P2) Priority Support Service Incidents means incidents that need to be dealt with quickly but do not prevent the use of the Subscription Services, including but not limited to incidents that prevent the use of a product feature; and 4.3. Normal (P3) Priority Support Service Incidents means incidents that are not urgent which can be dealt with on a first come first served basis including but not limited to minor incidents that do not prevent use of a feature; and 4.4. Low (P4) Priority Support Service Incidents means incidents that are not urgent which can be dealt with on a first come first served basis including but not limited to cosmetic incidents that do not prevent use of a feature or function.
AutoNDA by SimpleDocs
INCIDENT PRIORITISATION. Each Incident is given a priority of 1, 2 or 3 (“Priority”) based on the severity of the Incident and the Services being provided. Each Incident will be assigned an initial Priority by the Customer. This initial Priority will then be validated by Help Desk personnel who will notify Customer in the case of any proposed change of priority.
INCIDENT PRIORITISATION. Client shall promptly, following discovery, notify Supplier of any Error via the Helpdesk and provide Supplier with reasonable detail of the nature and circumstances of the Error. Each Party shall categorise Errors as follows:

Related to INCIDENT PRIORITISATION

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Project Planning GOVERNMENTAL APPROVALS; ENVIRONMENTAL COMPLIANCE; PUBLIC INFORMATION 30 4.1 Planning and Engineering Activities 30 4.2 Site Conditions 30 4.3 Governmental Approvals 30 4.4 Environmental Compliance 34 4.5 Community Outreach and Public Information 35

  • Workload Management 11.1 The parties to this Agreement acknowledge that employees and management have a responsibility to maintain a balanced workload and recognise the adverse affects that excessive workloads may have on employee/s and the quality of resident/client care. 11.2 To ensure that employee concerns involving excessive workloads are effectively dealt with by Management the following procedures should be applied: (a) Step 1: In the first instance, employee/s should discuss the issue with their immediate supervisor and, where appropriate, explore solutions. (b) Step 2: If a solution cannot be identified and implemented, the matter should be referred to an appropriate senior manager for further discussion. (c) Step 3: If a solution still cannot be identified and implemented, the matter should be referred to the Facility Manager for further discussion. (d) Step 4: The outcome of the discussions at each level and any proposed solutions should be recorded in writing and fed back to the effected employees. 11.3 Workload management must be an agenda item at staff meetings on at least a quarterly basis. Items in relation to workloads must be recorded in the minutes of the staff meeting, as well as actions to be taken to resolve the workloads issue/s. Resolution of workload issues should be based on the following criteria including but not limited to: (a) Clinical assessment of residents’ needs; (b) The demand of the environment such as facility layout; (c) Statutory obligation, (including, but not limited to, work health and safety legislation); (d) The requirements of nurse regulatory legislation; (e) Reasonable workloads (such as roster arrangements); (f) Accreditation standards; and (g) Budgetary considerations. 11.4 If the issue is still unresolved, the employee/s may advance the matter through Clause 9 Dispute Resolution Procedure. Arbitration of workload management issues may only occur by agreement of the employer and the employee representative, which may include the union/s.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • DESCRIPTION OF THE PROPERTY 13.1 The Property as referred to in the Proclamation of Sale shall be deemed to have been correctly and sufficiently described. 13.2 All intended bidders including the Purchaser shall be deemed to have sought independent legal advice, made necessary enquiries, searches and inspection of the Property and is satisfied with the identity, description, state and condition of the Property. 13.3 In the event of any error, misstatement, omission and/or misdescription of any kind relating to the Property in the Proclamation of Sale or any other documents, such error, misstatement, omission and/or misdescription shall not in any manner annul the sale, nor shall there be any adjustment of the Purchase Price nor shall compensation be allowed nor shall the Bank be open to any liability of any form. 13.4 If the land or floor area of the property is found to exceed that as described and additional payment is imposed for the excess area by the Developer and/or relevant authorities, then such additional payment shall be solely and absolutely borne and paid by the Purchaser 13.5 If the land or floor area of the property is found to be less that as described, any claim for the reduced area shall be undertaken solely by the Purchaser against the Developer and/or such party and neither the Assignee/ Bank , the Assignee/ Bank’s solicitors nor the Auctioneer shall in any way responsible or liable for such claim. The auction sale herein shall not be annulled and there shall not be any adjustment of the Purchase Price as a result of such shortfall in the area of the Property.

  • Maintenance of the Primary Mortgage Insurance Policies (a) The Master Servicer shall not take, or permit any Servicer (to the extent such action is prohibited under the applicable Servicing Agreement) to take, any action that would result in noncoverage under any applicable Primary Mortgage Insurance Policy of any loss which, but for the actions of such Master Servicer or Servicer, would have been covered thereunder. The Master Servicer shall use its best reasonable efforts to cause each Servicer (to the extent required under the related Servicing Agreement) to keep in force and effect (to the extent that the Mortgage Loan requires the Mortgagor to maintain such insurance), primary mortgage insurance applicable to each Mortgage Loan in accordance with the provisions of this Agreement and the related Servicing Agreement, as applicable. The Master Servicer shall not, and shall not permit any Servicer (to the extent required under the related Servicing Agreement) to, cancel or refuse to renew any such Primary Mortgage Insurance Policy that is in effect at the date of the initial issuance of the Mortgage Note and is required to be kept in force hereunder except in accordance with the provisions of this Agreement and the related Servicing Agreement, as applicable. (b) The Master Servicer agrees to present, or to cause each Servicer (to the extent required under the related Servicing Agreement) to present, on behalf of the Trustee and the Certificateholders, claims to the insurer under any Primary Mortgage Insurance Policies and, in this regard, to take such reasonable action as shall be necessary to permit recovery under any Primary Mortgage Insurance Policies respecting defaulted Mortgage Loans. Pursuant to Section 4.01 and 4.02, any amounts collected by the Master Servicer or any Servicer under any Primary Mortgage Insurance Policies shall be deposited in the Master Servicer Collection Account, subject to withdrawal pursuant to Section 4.03.

  • Continuity Except as expressly modified hereby, the terms and provisions of the Agreement and all instruments, agreements or other documents executed and delivered in connection therewith shall continue in full force and effect. Whenever the “Agreement” is referenced in the Agreement or any of the instruments, agreements or other documents executed and delivered in connection therewith, such references shall be deemed to mean the Agreement as modified hereby.

  • Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)

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