Framework scheme Sample Clauses

Framework scheme additional conditions 2.3.1 Conditions for derogation from the basic scheme ▪ The employer may operate a framework scheme under the following conditions. ▪ It must first have reached a written agreement with: ▪ The employer organises the consultations with the participation body and the employees concerned. The participation body may have itself be assisted by one or more trade union representatives. ▪ The term of any agreed framework scheme will be specified in the scheme. The term may never exceed that of this collective agreement. No tacit renewal of the scheme is allowed. ▪ The employer informs the parties to this CA about the agreements made. It must do so via the Construction & Infrastructure Technical Centre's digital desk (xxx.xxxxxx.xx). When doing so, the employer must provide evidence of the required agreement with the participation body and employees. ▪ As long as a framework scheme has not been reported to the Construction & Infrastructure Technical Centre, the basic scheme will continue to apply within the company. ▪ The employer evaluates the implementation of the agreements concluded. It will inform the parties to the CA of the outcome at their request. Such information is provided via the Construction & Infrastructure Technical Centre. 2.3.2 Conditions for derogation from the framework scheme ▪ If the employer wishes to make arrangements that go beyond the limits of the framework scheme, it may do so only once: - the employees' organisations FNV and CNV Vakmensen have agreed to this and - it has informed the parties to the CA about the agreements reached; such information is provided via the Construction & Infrastructure Technical Centre.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Framework scheme

  • Framework This Agreement establishes a framework that will enable Red Hat to provide Software and Services to Client. “Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. The specific services (the “Services”) and/or Software that Red Hat will provide to Client will be described in an Order Form, signed by the parties or otherwise accepted by Red Hat, which may consist of (a) one or more mutually agreed order forms, statements of work, work orders or similar transaction documents, or (b) an order placed by Client through Red Hat's online store accessible from a Red Hat website. The parties agree that the terms of this Agreement will govern all purchases and use by Client of Software and Services unless otherwise agreed by the parties in writing.

  • Nature of Scheme The Company specifically intends that the Plan will not be an occupational retirement scheme for purposes of the Occupational Retirement Schemes Ordinance.

  • Framework Agreement 4.1.2.1 The Parties shall enter into a Framework Agreement within 28 days after the Contractor receives the Letter of Acceptance, unless the Particular Conditions establish otherwise. The Framework Agreement shall be based upon FORM No. 3 – FRAMEWORK AGREEMENT annexed to the Particular Conditions. The costs of stamp duties and similar charges (if any) imposed by law in connection with entry into the Framework Agreement shall be borne by the Procuring Entity. 4.1.2.2 The Framework Agreement establishes the terms and conditions that will govern the contract awarded during the term of the Framework Agreement. The Framework Agreement establishes for the procurement works by package as and when required, over the specified period of time. The Framework Agreement does not commit a Procuring Entity to procure, nor a Firm to supply. The Framework Agreement allows the Procuring Entity to call the Contractor to commence the works on a particular package in a specified location within the duration of the agreement. 4.1.2.3 This Framework Agreement does not guarantee the contractor of being called for a contract to start and no commitment is made with regard to possible number of packages to carry out. 4.1.2.4 This Framework Agreement does exclude the Procuring Entity from the right to procure the same Works from other firms. 4.1.2.5 This Framework Agreement does not stop the Procuring Entity from removing the contractor from the same Agreement. 4.1.2.6 FAs shall be established for a maximum period of three (3) years. The Procuring Entity may with the Consent of the Contractor extend this Agreement if the agreement period is less than three (3) years, if the initial engagement has been satisfactory. 4.1.2.7 Call-off Contracts; for work on a package to start, the Procuring Entity shall issue a notice of acceptance of a particular package requesting the contractor to furnish a Performance Security and to start the works thereafter, and providing the contractor with details of location where the works, are to be carried out. The call-off statement shall specify the objectives, tasks, deliverables, timeframes and price or price mechanism. The price for individual call-off contracts shall be based on the prices detailed in the Framework Agreement.

  • FRAMEWORK AGREEMENT MANAGEMENT The Parties shall manage this Framework Agreement in accordance with Schedule 14 (Framework Management).

  • MINISTRY INITIATIVES OSSTF/FEESO education workers will be an active participant in the consultation process at the Ministry Initiatives Committee. Ministry Initiatives Committee shall meet at least quarterly each year to discuss new initiatives, including implications for training, resources.

  • EGM The EGM will be convened and held for the purpose of considering and, if thought fit, approving the issue of Warrants and the transactions contemplated thereunder, including the issue of Warrant Shares upon exercise of the Warrants. To the best knowledge of the Directors, none of the Shareholders has a material interest in the transactions contemplated under the issue of Warrants, accordingly, no Shareholders will be required to abstain from voting at the EGM.

  • MINISTRY/SCHOOL BOARD INITIATIVES ETFO will be an active participant in the consultation process to develop a Ministry of Education PPM regarding Ministry/School Board Initiatives.

  • STRATEGIC PLAN (1) Within one hundred twenty (120) days, the Board shall adopt, implement, and thereafter ensure Bank adherence to a written strategic plan for the Bank covering at least a three-year period. The strategic plan shall establish objectives for the Bank's overall risk profile, earnings performance, growth, balance sheet mix, off-balance sheet activities, liability structure, capital adequacy, reduction in the volume of nonperforming assets, product line development and market segments that the Bank intends to promote or develop, together with strategies to achieve those objectives and, at a minimum, include: (a) a mission statement that forms the framework for the establishment of strategic goals and objectives; (b) an assessment of the Bank's present and future operating environment; (c) the development of strategic goals and objectives to be accomplished over the short and long term; (d) an identification of the Bank’s present and future product lines (assets and liabilities) that will be utilized to accomplish the strategic goals and objectives established in (1 )(c) of this Article; (e) an evaluation of the Bank's internal operations, staffing requirements, board and management information systems and policies and procedures for their adequacy and contribution to the accomplishment of the goals and objectives developed under (1)(c) of this Article; (f) a management employment and succession program to promote the retention and continuity of capable management; (g) product line development and market segments that the Bank intends to promote or develop; (h) an action plan to improve bank earnings and accomplish identified strategic goals and objectives, including individual responsibilities, accountability and specific time frames; (i) a financial forecast to include projections for major balance sheet and income statement accounts and desired financial ratios over the period covered by the strategic plan; (j) control systems to mitigate risks associated with planned new products, growth, or any proposed changes in the Bank’s operating environment; (k) specific plans to establish responsibilities and accountability for the strategic planning process, new products, growth goals, or proposed changes in the Bank’s operating environment; and (l) systems to monitor the Bank’s progress in meeting the plan’s goals and objectives. (2) Upon adoption, a copy of the plan shall be forwarded to the Assistant Deputy Comptroller for review and prior written determination of no supervisory objection. Upon receiving a determination of no supervisory objection from the Assistant Deputy Comptroller, the Bank shall implement and adhere to the strategic plan. (3) The Board shall ensure that the Bank has processes, personnel, and control systems to ensure implementation of and adherence to the plan developed pursuant to this Article.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

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