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. CHANGES TO THE ORIGINAL LEARNING AGREEMENT 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.
Technical Support State Street will provide technical support to assist the Fund in using the System and the Data Access Services. The total amount of technical support provided by State Street shall not exceed 10 resource days per year. State Street shall provide such additional technical support as is expressly set forth in the fee schedule in effect from time to time between the parties (the “Fee Schedule”). Technical support, including during installation and testing, is subject to the fees and other terms set forth in the Fee Schedule.
Data Collection Some downloaded software included in the Materials may generate and collect information about the software and usage and transmit it to Intel to help improve Intel’s products and services. This collected information may include product name, product version, time of event collection, license type, support type, installation status, hardware and software performance, and use. 9.
Project Approach Project schedules and budgets are reviewed by the Project Manager on a weekly basis during our company-wide Project Managers Meeting using project status reports generated by our control software (Deltek Vision). Progress is compared to the schedule and budget to ensure adequate resources are available and that necessary coordination is occurring. Costs are reported real time, with actual labor based on time sheet entry and actual expense costs based on invoices. The reporting system can be customized to track specific tasks or efforts in multiple categories, making it flexible enough to adapt to any project specific requirements. We hold regular project coordination meetings to facilitate communication and information transfer among the design team. These meetings are held weekly and are supplemented with e-mail communication, as well as telephone conversations. We hold monthly project status meetings with your project manager to update project status, discuss priorities, and receive direction from City staff. This provides an opportunity for communication and information to flow openly between the City and the design team. These meetings are supplemented by communications that will occur via e-mail and telephone. We conduct meetings with other agencies and stakeholders impacted by the work as needed. E-mail and telephone communication work well for quick questions or minor issues, but we have found that the most effective means of communication with other agencies and stakeholders is the “old-fashioned” face- to-face mexxxxx. Xxbble’s record of providing quality civil engineering services to our clients reflects our ability to manage multiple projects effectively and efficiently. Our philosophy is that each project is personally overseen by one of our principal officers, thereby providing immediate attention to all project aspects (i.e. negotiations, communications, schedule, budgets).
Notice to Proceed - Site Improvements The Recipient shall not commence, or cause to be commenced, any site improvements or other work on the Land until the Director has issued a Notice to Proceed to the Recipient. Such Notice to Proceed will not be issued until the Director is assured that the Recipient has complied with all requirements for the approval of a grant under Revised Code Sections 164.20 through 164.27 and has completed any land acquisition required by the Project. A Notice to Proceed shall be required for all Project prime contractors or direct procurement initiated by the Recipient following execution of this Agreement.
Notice to Proceed (NTP Following the JOA and purchase order issuance, the County will issue a Notice to Proceed (NTP) that will provide the construction start date, the Work duration period, and the Substantial Completion date. The Contractor agrees to begin and complete construction within the dates specified on the NTP. The County must approve all extensions of time in writing. The County may also issue an Emergency Notice to Proceed (NTP). In the event the County requires the Contractor to respond to an immediate request for work, a Job Order will be created and an Emergency NTP will be issued. The Contractor will be required to perform the Scope of Work included with the Emergency NTP as directed by the County’s Project Manager or designee. The Detailed Scope of Work, Quotation, Subcontractor Listing, Shop Drawings and required Non Pre-priced backup documentation will be submitted upon completion of the emergency work in accordance with the Ordering Procedures detailed in Section III above.
LOT OVERVIEW This Contract encompasses the Lots listed in Appendix D – Contractor and Reseller Information. The following descriptions, as applicable, delineate the scope of the awarded Lots.
Project Overview The Statement of Work (SOW) documents the Project Scope, methodology, roles and responsibilities, implementation Stages, and deliverables for the implementation of Tyler products. The Project goals are to offer City of Xxxxx Creek, GA the opportunity to make the City more accessible and responsive to external and internal customer needs and more efficient in its operations through: Streamlining, automating, and integrating business processes and practices Providing tools to produce and access information in a real‐time environment Enabling and empowering users to become more efficient, productive and responsive Successfully overcoming current challenges and meeting future goals
Terminal Receipt You can get a receipt at the time you make any transaction (except inquiries) involving your account using an ATM and/or point-of-sale (POS) terminal.
Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").