Identification of possible scenarios and specific actions Sample Clauses

Identification of possible scenarios and specific actions. According to the previous experience in previous distributed EU funded projects some financial deviation could occur into the project life-time. Of course deviations between a preliminary plan (as the one provided at the proposal stage) and the real detailed action plan (as the one produced at the beginning of the project according to the inception report details) will always occur. 3EMOTION project will have therefore a degree of flexibility in accepting minor deviation between original plans and actual reporting, as outlined in the following paragraphs. Nevertheless, according to our experience, some deviations could occur having a destabilization impact on plans and project outputs. Below are listed some of the “usual” deviations that could occur during the project lifetime and that the Quality financial control should identify and solved: - Deviation in PM allocations: o Partner will use a number of PM in a ratio not allowed by the project, especially if analysed at WP level. Deviations at WP level (even if this deviation will not appear globally to the partner level) will not be accepted by the management team. In order to avoid deviations at WP level, the financial control will be done at WP level. o Sometimes partners use an actual average monthly salary rate different from the one identified at the project proposal stage. In order to reach the expected personnel cost value, partners tend to adjust accordingly the number of persons/months. This adjustment to reach expected value on personnel cost will not be accepted. In order to avoid this solution, 3EMOTION will apply an analysis of deviation to persons/months rate by itself. - Deviation in Cost allocations: o Sometimes, partner budget allocation to different cost categories, as identified at the proposal stage, differs from the real implementation plans. 3EMOTION will try to avoid any budget transfer between different cost categories inn order to keep a strong coherence with planned budget structure. According with this basic approach 3EMOTION will evaluate deviations in cost categories, measuring cost deviations (planned versus actual) within each of the following categories: ▪ Personnel cost ▪ Travel costs ▪ Other direct costs ▪ Indirect costs Not accepting any major deviation (see its definition in the following paragraph) within each of the mentioned category In order to apply a standard contingency plans on previous outlined deviations, 3EMOTION project has applied its own micro-management r...
Sample 1
AutoNDA by SimpleDocs

Related to Identification of possible scenarios and specific actions

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

  • Approval of Plans and Specifications The Plans and Specifications will conform to the requirements and conditions set out by applicable law or any effective restrictive covenant, and to all governmental authorities which exercise jurisdiction over the Leased Premises or the construction thereon.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Regulation AB Compliance; Intent of Parties; Reasonableness The parties hereto acknowledge that interpretations of the requirements of Regulation AB may change over time, whether due to interpretive guidance provided by the Commission or its staff, consensus among participants in the asset-backed securities markets, advice of counsel, or otherwise, and agree to comply with requests made by the Depositor or the Master Servicer in good faith for delivery of information under these provisions on the basis of evolving interpretations of Regulation AB. In connection with the Trust, the Servicer shall cooperate fully with the Master Servicer and the Depositor to deliver to the Master Servicer and/or the Depositor (including its assignees or designees), any and all statements, reports, certifications, records and any other information available to such party and reasonably necessary in the good faith determination of the Depositor or the Master Servicer to permit the Depositor to comply with the provisions of Regulation AB, together with such disclosures relating to the Servicer reasonably believed by the Depositor or the Master Servicer to be necessary in order to effect such compliance.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • Regulatory and Special Allocations Notwithstanding the provisions of Section 6.1: (a) If there is a net decrease in Company Minimum Gain (determined according to Treasury Regulations Section 1.704-2(d)(1)) during any Fiscal Year, each Member shall be specially allocated income and gain for such Fiscal Year (and, if necessary, subsequent Fiscal Years) in an amount equal to such Member’s share of the net decrease in Company Minimum Gain, determined in accordance with Treasury Regulations Section 1.704-2(g). The items to be so allocated shall be determined in accordance with Treasury Regulations Sections 1.704-2(f)(6) and 1.704-2(j)(2). This Section 6.2(a) is intended to comply with the “minimum gain chargeback” requirement in Treasury Regulation Section 1.704-2(f) and shall be interpreted consistently therewith. (b) Member Nonrecourse Deductions shall be allocated in the manner required by Treasury Regulations Section 1.704-2(i). Except as otherwise provided in Treasury Regulations Section 1.704-2(i)(4), if there is a net decrease in Member Nonrecourse Debt Minimum Gain during any Fiscal Year, each Member that has a share of such Member Nonrecourse Debt Minimum Gain shall be specially allocated income and gain for such Fiscal Year (and, if necessary, subsequent Fiscal Years) in an amount equal to that Member’s share of the net decrease in Member Nonrecourse Debt Minimum Gain. Items to be allocated pursuant to this paragraph shall be determined in accordance with Treasury Regulations Sections 1.704-2(i)(4) and 1.704-2(j)(2). This Section 6.2(b) is intended to comply with the “minimum gain chargeback” requirements in Treasury Regulations Section 1.704-2(i)(4) and shall be interpreted consistently therewith. (c) In the event any Member unexpectedly receives any adjustments, allocations or Distributions described in Treasury Regulations Section 1.704-1(b)(2)(ii)(d)(4), (5) or (6), income and gain shall be specially allocated to such Member in an amount and manner sufficient to eliminate the Adjusted Capital Account Deficit created by such adjustments, allocations or Distributions as quickly as possible. This Section 6.2(c) is intended to comply with the qualified income offset requirement in Treasury Regulations Section 1.704-1(b)(2)(ii)(d) and shall be interpreted consistently therewith. (d) The allocations set forth in paragraphs (a), (b) and (c) above (the “Regulatory Allocations”) are intended to comply with certain requirements of the Treasury Regulations under Code Section 704. Notwithstanding any other provisions of this Article VI (other than the Regulatory Allocations), the Regulatory Allocations shall be taken into account in allocating Net Income and Net Losses among Members so that, to the extent possible, the net amount of such allocations of Net Income and Net Losses and other items and the Regulatory Allocations to each Member shall be equal to the net amount that would have been allocated to such Member if the Regulatory Allocations had not occurred. (e) The Company and the Members acknowledge that allocations like those described in Proposed Treasury Regulation Section 1.704-1(b)(4)(xii)(c) (“Forfeiture Allocations”) result from the allocations of Net Income and Net Loss provided for in this Agreement. For the avoidance of doubt, the Company is entitled to make Forfeiture Allocations and, once required by applicable final or temporary guidance, allocations of Net Income and Net Loss shall be made in accordance with Proposed Treasury Regulation Section 1.704-1(b)(4)(xii)(c) or any successor provision or guidance.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

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