ARCP Programme Sample Clauses

ARCP Programme. 5th December 2014
Sample 1
AutoNDA by SimpleDocs

Related to ARCP Programme

  • Programme 13.1 Within the time stated in the Contract Data, the Contractor shall submit to the Engineer for approval a Programme showing the general methods, arrangements,' order and timing for all the activities for the construction of works. 13.2 The program shall be supported with all the details regarding key personnel, equipment and machinery proposed to be deployed on the works for its execution. The contractor shall submit the list of equipment and machinery being brought to site, the list of key personnel being deployed, the list of machinery/equipment being placed in field laboratory and the location of field laboratory along with the Programme.

  • PROPOSED MOBILITY PROGRAMME The proposed mobility programme includes the indicative start and end months of the agreed study programme that the student will carry out abroad. The Learning Agreement must include all the educational components to be carried out by the student at the receiving institution (in table A) and it must contain as well the group of educational components that will be replaced in his/her degree by the sending institution (in table B) upon successful completion of the study programme abroad. Additional rows can be added as needed to tables A and B. Additional columns can also be added, for example, to specify the study cycle-level of the educational component. The presentation of this document may also be adapted by the institutions according to their specific needs. However, in every case, the two tables A and B must be kept separated, i.e. they cannot be merged. The objective is to make clear that there needs to be no one to one correspondence between the courses followed abroad and the ones replaced at the sending institutions. The aim is rather that a group of learning outcomes achieved abroad replaces a group of learning outcomes at the sending institution, without having a one to one correspondence between particular modules or courses. A normal academic year of full-time study is normally made up of educational components totalling 60 ECTS* credits. It is recommended that for mobility periods shorter than a full academic year, the educational components selected should equate to a roughly proportionate number of credits. In case the student follows additional educational components beyond those required for his/her degree programme, these additional credits must also be listed in the study programme outlined in table A. When mobility windows are embedded in the curriculum, it will be enough to fill in table B with a single line as described below: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Mobility window … Total: 30 Otherwise, the group of components will be included in Table B as follows: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Course x … 10 Module y … 10 Laboratory work … 10 Total: 30 The sending institution must fully recognise the number of ECTS* credits contained in table A if there are no changes to the study programme abroad and the student successfully completes it. Any exception to this rule should be clearly stated in an annex of the Learning Agreement and agreed by all parties. Example of justification for non-recognition: the student has already accumulated the number of credits required for his/her degree and does not need some of the credits gained abroad. Since the recognition will be granted to a group of components and it does not need to be based on a one to one correspondence between single educational components, the sending institution must foresee which provisions will apply if the student does not successfully complete some of the educational components from his study programme abroad. A web link towards these provisions should be provided in the Learning Agreement. The student will commit to reach a certain level of language competence in the main language of instruction by the start of the study period. The level of the student will be assessed after his/her selection with the Erasmus+ online assessment tool when available (the results will be sent to the sending institution) or else by any other mean to be decided by the sending institution. A recommended level has been agreed between the sending and receiving institutions in the inter-institutional agreement. In case the student would not already have this level when he/she signs the Learning Agreement, he/she commits to reach it with the support to be provided by the sending or receiving institution (either with courses that can be funded by the organisational support grant or with the Erasmus+ online tutored courses). All parties must sign the document; however, it is not compulsory to circulate papers with original signatures, scanned copies of signatures or digital signatures may be accepted, depending on the national legislation. * In countries where the "ECTS" system it is not in place, in particular for institutions located in partner countries not participating in the Bologna process, "ECTS" needs to be replaced in all tables by the name of the equivalent system that is used and a weblink to an explanation to the system should be added. The section to be completed during the mobility is needed only if changes have to be introduced into the original Learning Agreement. In that case, the section to be completed before the mobility should be kept unchanged and changes should be described in this section. Changes to the mobility study programme should be exceptional, as the three parties have already agreed on a group of educational components that will be taken abroad, in the light of the course catalogue that the receiving institution has committed to publish well in advance of the mobility periods and to update regularly as ECHE holder. However, introducing changes might be unavoidable due to, for example, timetable conflicts. Other reasons for a change can be the request for an extension of the duration of the mobility programme abroad. Such a request can be made by the student at the latest one month before the foreseen end date. These changes to the mobility study programme should be agreed by all parties within four to seven weeks (after the start of each semester). Any party can request changes within the first two to five-week period after regular classes/educational components have started for a given semester. The exact deadline has to be decided by the institutions. The shorter the planned mobility period, the shorter should be the window for changes. All these changes have to be agreed by the three parties within a two-week period following the request. In case of changes due to an extension of the duration of the mobility period, changes should be made as timely as possible as well. Changes to the study programme abroad should be listed in table C and, once they are agreed by all parties, the sending institution commits to fully recognise the number of ECTS credits as presented in table C. Any exception to this rule should be documented in an annex of the Learning Agreement and agreed by all parties. Only if the changes described in table C affect the group of educational components in the student's degree (table B) that will be replaced at the sending institution upon successful completion of the study programme abroad, a revised version should be inserted and labelled as "Table D: Revised group of educational components in the student's degree that will be replaced at sending institution". Additional rows and columns can be added as needed to tables C and D. All parties must confirm that the proposed amendments to the Learning Agreement are approved. For this specific section, original or scanned signatures are not mandatory and an approval by email may be enough. The procedure has to be decided by the sending institution, depending on the national legislation.

  • Development Program RWJPRI shall be [**] and have [**] in consultation with the JDAC, to select LICENSED COMPOUNDS which shall then be designated PRODUCTS for further DEVELOPMENT by RWJPRI and marketing by ORTHO and its AFFILIATES. RWJPRI shall provide KOSAN with written notice of its decision to select a LICENSED COMPOUND for DEVELOPMENT. Once a PRODUCT has been selected for further DEVELOPMENT, RWJPRI, with the advice of the JDAC, shall have the [**] right to develop the PRODUCT through STAGES O, I, II and III and shall have the [**] right to prepare and file, and shall be the owner of, all applications for MARKETING AUTHORIZATION throughout the world. During such DEVELOPMENT efforts, KOSAN will assist RWJPRI as may be mutually agreed, at RWJPRI's expense, in chemical development, formulation development, production of labeled material and production of sufficient quantities of material for STAGE O and initial STAGE I studies. RWJPRI shall exercise diligent efforts, commensurate with the efforts it would normally exercise for products with similar potential sales volume and consistent with its overall business strategy, in developing such PRODUCT in accordance with the DEVELOPMENT PLAN established by RWJPRI. In the course of such efforts RWJPRI shall, either directly or through an AFFILIATE or SUBLICENSEE to which the license shall have been extended, take appropriate steps including the following: (i) in consultation with the JDAC, select certain LICENSED COMPOUNDS for STAGE O DEVELOPMENT; and (ii) establish and maintain a program reasonably designed, funded and resourced to obtain information adequate to enable the preparation and filing with an appropriate and properly empowered national regulatory authority all necessary documentation, data and [**] CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. other evidence required for IND non-rejection to commence and conduct human clinical trials of such PRODUCT. (iii) proceed following IND non-rejection to commence PHASE I, II, and III clinical trials, associated studies and such other work which RWJPRI reasonably deems to be required for subsequent inclusion in filings for MARKETING AUTHORIZATION; (iv) after such submissions are filed prosecute such submissions and file all reasonably necessary, reports and respond to all reasonable requests from the pertinent regulatory, authorities for information, data, samples, tests and the like.

  • Maintenance Programme (i) The Contractor shall prepare a monthly maintenance programme (the “Maintenance Programme”) in consultation with the Authority’s Engineer and submit the same to the Authority’s Engineer not later than 10 (ten) days prior to the commencement of the month in which the Maintenance is to be carried out. For this purpose a joint monthly inspection by the Contractor and the Authority’s Engineer shall be undertaken. The Maintenance Programme shall contain the following: (a) The condition of the road in the format prescribed by the Authority’s Engineer; (b) the proposed maintenance Works; and (c) deployment of resources for maintenance Works.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • 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.

  • Research Program The term “Research Program” shall mean the research program to be undertaken by TSRI under the direction and control of the Principal Investigator as expressly set forth on Exhibit A hereto.

  • Collaboration 31.1 If the Buyer has specified in the Order Form that it requires the Supplier to enter into a Collaboration Agreement, the Supplier must give the Buyer an executed Collaboration Agreement before the Start date. 31.2 In addition to any obligations under the Collaboration Agreement, the Supplier must: 31.2.1 work proactively and in good faith with each of the Buyer’s contractors 31.2.2 co-operate and share information with the Buyer’s contractors to enable the efficient operation of the Buyer’s ICT services and G-Cloud Services

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Safety Program The Contractor shall design a specific safety program for the Work for the site(s). The Contractor shall establish and require all Subcontractors to establish reasonable safety programs. The Contractor shall also submit its standard monthly safety reports to the Owner and Design Professional. No imposition of responsibility on the Contractor for safety under this Contract shall relieve any subcontractor of its responsibility for safety of persons or property on or near the Project Site. The Contractor shall include in his plant he names of the person in charge of Safety.

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