Other Assumptions. Participant Liabilities shall be determined based on the assumption that the Plan is terminated at such date of valuation and having regard, for greater certainty, to the value of any benefits previously paid to the Participant pursuant to the Plan.
Other Assumptions. GMAC commits to incorporating all relevant assumptions necessary to estimate [***] • As previously agreed by GM and GMAC, [***] • Other assumptions used in the pricing models could include: • [***] • [***] • [***] • [***] • [***] • GMAC will develop methodologies and update the other pricing model assumptions [***] Updates may be as frequent as monthly, but are more likely to be on a quarterly, semi-annual, or annual basis as these items can be time-consuming to update and do not generally change appreciably over short periods of time EXHIBIT C
Other Assumptions. The services under this Agreement are being provided based upon the following assumptions, in addition to any assumption or detail stated in the rest of the document: • Following agreement to close a ticket from the Customer the ticket will be closed in the Supplier Service Desk. • Once closed, the ticket process will be considered finished and will not be re-opened. • The Customer will provide the Supplier with any known tasks, either one off or regular, to aid with forward planning. • The Service Owner will, when needed, be the escalation route should any issues arise with non-satisfactory delivery or performance from third party suppliers. • For the purposes of clarification and to avoid confusion it is the Supplier’s understanding that the Customer owns: o All the data within the application databases o All application licences
Other Assumptions. (i) All drafts of the documents that we have examined will be executed by the parties in the form of the drafts examined.
Other Assumptions. The services under this Agreement are being provided based upon the following assumptions, in addition to any assumption or detail stated in the rest of the document: • Following agreement to close a ticket from the Customer the ticket will be closed in the Supplier Service Desk. • Once closed, the ticket process will be considered finished and will not be re-opened. • The Customer will provide the Supplier with any known tasks, either one off or regular, to aid with forward planning. • The Service Owner will, when needed, be the escalation route should any issues arise with non-satisfactory delivery or performance from third party suppliers. • For the purposes of clarification and to avoid confusion it is HPS’s understanding that the Customer owns: o All the data within the application databases o All application licences B4.6 Incident / Problem Management Incident Management services include all activities to be performed in conjunction with identification and correction of unplanned or unexpected application functionality bugs, or defects encountered by the Customer users which are affecting either the production, development or the test environment in this Agreement. For any ticket assigned to the Supplier as an incident, the Supplier will investigate the cause of the problem and provide a fix, solution or work around for the problem. Appropriate information relevant to the ticket will be documented to enable better incident tracking and reporting. In case changes need to be implemented on the production environment, such changes must first be approved through the quality assurance process, in accordance with relevant change management procedure before being implemented. When relevant, the Supplier will also perform problem management. Where the Supplier identifies a common root cause for a high number of such tickets, the Supplier will report it to the Customer and in collaboration with the Customer IT Service Manager, define a solution and a resolution plan. Depending on the root cause nature, the Customer and Supplier will jointly decide through which service the resolution should be addressed.
Other Assumptions. (v) There have been no amendments made to the documents listed in Schedule 1 (Documents and Enquiries) which would affect this Opinion Letter. SCHEDULE 3
Other Assumptions. The fee schedule assumes that there will be two (2) classes of shares. Also, this schedule reflects the fact that the fund will not declare a daily distribution, but will distribute monthly or annually only. Increases in the number of classes or any change in the frequency of distributions will result in an increase in the fees noted above. This fee schedule does not reflect the impact, if any, on IBT's processing transactions using FundServe or other NSCC applications. The fees associated with such applications and any related systems development costs will be determined at a later date prior to implementation. The above fees will be charged against the funds' custodian checking account five business days after the invoice is mailed to the fund.
Other Assumptions. The fee schedule assumes that there will be two (2) classes of shares. Also, this schedule reflects the fAct that the Fund will not declare a daily distribution, but will distribute monthly or annually only. increases in the number of classes or any change in the frequency of distributions will result in an increase in the fees noted above. This fee schedule does not reflect the impAct, if any, on ibt's processing transactions using Fundserve or other nscc applications. the fees associated with such applications and any related Systems development costs will be determined at a later date prior to implementation. The above fees will be charged against the Funds' custodian checking Account five business days after the invoice is mailed to the Fund. This annual fee schedule is valid for 30 days and assumes the execution of IBT's standard contrActual Agreements for a minimum term of one (1) year. All charges will be billed monthly. The fee schedule will be effective upon start-up of the Fund.
Other Assumptions. As projected by the Company and agreed by IFC. SCHEDULE 6 Page 1 of 2 FORM OF LETTER TO COMPANY’S AUDITORS (See Section 5.03(f) (Additional Conditions of First A Loan) and Section 6.01(e) (Affirmative Covenants) of the Loan and Guarantee Agreement) [Company’s Letterhead] [Date] [NAME OF AUDITORS] [ADDRESS] Ladies and Gentlemen: We hereby authorize and request you to give to International Finance Corporation of 2000 Xxxxxxxxxxxx Xxxxxx, X.X., Xxxxxxxxxx, X.X. 00000, Xxxxxx Xxxxxx of America (“IFC”), all such information as IFC may reasonably request with regard to the financial statements (both audited and unaudited), accounts and operations of the undersigned company. We have agreed to supply that information and those statements under the terms of a Loan and Guarantee Agreement between the undersigned company and IFC (amongst others) dated December ___, 2006 (the “Loan Agreement”). For your information we enclose a copy of the Loan Agreement. We authorize and request you to send two copies of the audited accounts of the undersigned company to IFC to enable us to satisfy our obligation to IFC under Section 6.03 (b) (i) of the Loan Agreement. When submitting the same to IFC, please also send, at the same time, a copy of your full report on such accounts in a form reasonably acceptable to IFC. Please note that under Section 6.03 (b) (ii) and (iii) and Section 6.03 (c) of the Loan Agreement, we are obliged to provide IFC with:
