Exception Handling Sample Clauses

Exception Handling. Notwithstanding anything to the contrary set forth in Section 4(a), if there is a Material Adverse Exception Event, then the rules and procedures set forth in this clause "(b)" shall determine the rights and obligations of the DAO Members relating to the DAO Property. (i) Exception Notice.* If any DAO Member becomes aware that there is a Material Adverse Exception Event, such DAO Member (the “***Sending Member***”) shall deliver to the other DAO Members (the “***Receiving Members***”) a notice (an “***Exception Notice***”): (A) certifying that the Sending Member believes in good faith that there is a Material Adverse Exception Event; (B) describing in reasonable detail the events, facts, circumstances and reasons forming the basis of such belief; (C) if and only if desired, describing in reasonable detail a proposal by such DAO Member of the actions to be taken, the agreements to be entered into, and the remedies to be sought by the DAO Members in response to the Material Adverse Exception Event an “***Exception Handling Proposal***”; (D) including copies of any written evidence or other material written information, and summaries of any other evidence, relevant to, and material for the consideration of, the Material Adverse Exception Event and the other matters referred to in the Exception Notice; and (E) containing a representation by the Sending Member, made to and for the benefit of the Receiving Members with the understanding that the Receiving Members will rely thereon, that, to the Sending Member’s knowledge, the certification and statements made pursuant to the preceding clauses “(A)” and “(B)” are accurate as of the date of the Exception Notice, and, considered collectively, do not contain any untrue statement of a material fact or omit to state any material fact necessary in order to make such statements, in light of the circumstances in which they were made, not misleading. (ii) Exception Standstill.* During the period starting on the date of delivery of an Exception Notice and ending with the DAO Members entering into an Exception Handling Addendum or receiving a final decision of an arbitrator in accordance with Section 4(b)(iii) (the “***Standstill Period***”), each DAO Member shall: (A) treat all of the Distributed DAO Property of such DAO Member that may have been Transferred to such DAO Member as a result of the Material Adverse Exception Event as if it were DAO Property, including by disregarding the parenthetical exceptions for Distribut...

Exception Handling. Recovery and Back up BMP stores all information about a job in its database. At a restart, BMP starts from the last unprocessed file. For example, if a job consists of ten files and an error occurs at file three, BMP starts with file four at start-up. BMP also features on-line back up using internal BMP features.

Exception Handling. Analysis of the capacity incidents/events to take the necessary measures to prevent their new occurrence

Exception Handling. Exceptions to policy typically require a formal documentation process including a formal acceptance by the corporate owner of the system or process.

Exception Handling. 16.1. While it is expected the Service Levels will be applied to all portfolio transfer activity, there may be times when the Participants decide to ‘opt out’ of some aspects. If the activity relates to one of the exceptions listed in section 6 (Exception Handling), such as dealing with a bulk client portfolio transfer request, then the process in section 6 will apply. If the Participants want to opt out of complying with the Service Levels in any other circumstance, this can only be done in accordance with the Contract Terms (which includes notifying TeX of the agreement to opt out within 2 Business Days). 16.2. In-flight transactions: 16.2.1. This term is intended to cover such items as pending acquisitions and disposals. The formal definition is in the UKETRG guidance referred to in section 2.2. 16.2.2. The Ceding Party will decide to accept the initial request in respect of those assets that can be transferred or indicate a pending transaction.

Exception Handling. 6.1. Where a Participant receives a request that cannot be processed (for instance due to invalid customer details), a reject notification should be issued to the sending party within the stated service level. 6.2. Where a Participant receives a request that cannot be processed within the service level due to one of the exception cases listed below, a delay notification should be issued to the sending party within the stated service level. Delay notifications may only be used for the exception cases listed below. 6.3. The following (which are explained further in section 15) are exceptions to normal processes that do not fit completely into the processes in section 5 above and/or which cannot be completed within the timescales in section 5: • In-flight transactions • Residual income • Bulk transfers • Cancellation/Cooling-off period reversal • Exit fee handling • Client authorisation • Pending conversions • Transfer pack • Red and amber pension scam flags • ‘Stronger Nudge’ requirements 6.4. The principles to be followed for in-flight transactions, residual income and bulk transfers are that: (i) discussions will be held between the Participants and agreement reached on how the Transfer will be handled, (ii) the UKETRG and Conversions Group messages should be (but are not required to be) used to implement what was agreed, and (iii) the Service Levels will then apply unless the Participants agree to the contrary. Where the exception handling process isto be initiated, or has already been agreed, by the Participants the Ceding Party must acknowledge receipt of a Portfolio Transfer Request in accordance with the Service Levels. 6.5. Illustrative examples are shown in the Guidance Notes in section 15 below. Section 15 also sets out guidance on cancellation/cooling-off period reversals.

Exception Handling. Requests for an exception to this Policy must include a documented business justification that is approved by the Managing Director of the business unit and submitted to the Chief Risk Officer for review. The Chief Risk Officer will inform the approving department head of a decision within two business days of receiving the request. Policy Owners: ▇▇▇▇ ▇▇▇▇▇▇, Managing Director and Chief Risk Officer ▇▇▇▇ ▇▇▇▇▇▇▇▇, Managing Director of Operations and Information Technology Effective Date: June 21, 2010 Access Administrator - an authorized Workforce Member responsible for creating and managing system access accounts. Application Owner - the application’s largest stakeholder, usually the owner of the primary business functions served by the application. Auto- forward rule - setting up parameters in Microsoft Outlook to facilitate automated forwarding or redirection of any message, which matches specific characteristics, to another e-mail account. Chain email or letter - email sent to successive people. Typically the body of the note has direction to send out multiple copies of the note and promises good luck or money if the direction is followed. Data owner - person who can authorize or deny access to certain data and is responsible for its accuracy, integrity, and timeliness. Email - the electronic transmission of information through a mail protocol such as SMTP or IMAP. Encryption - process of making data unreadable except to those who have a way to decrypt it using a special process, usually referred to as a key. Intellectual Property - includes, but is not limited to, inventions, improvements, discoveries, methods, developments, software, and works of authorship, whether patentable, trademarkable, copyrightable or not, which are created, made, conceived or reduced to practice by an employee during employment with First Marblehead, whether or not during normal working hours or on the premises of First Marblehead. For the purposes of this Standard, “Intellectual Property” does not include anything which does not relate to the business or research and development conducted or planned to be conducted by First Marblehead at the time it is created, made, conceived or reduced to practice and which is created, made, conceived or reduced to practice by the employee not during normal working hours, not on First Marblehead’s premises and not using First Marblehead’s tools, devices, equipment or Proprietary Information. Malware - software of malicious intent/impact ...

Exception Handling. Company may choose additional Exception handling options within the Lockbox Service. Some options are listed below:

Exception Handling. 8.1. Exceptions Due to Errant CIS/AMS Data or Data that Can Not be Verified