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.
Program Overview Microsoft extends to eligible partners the opportunity to participate in the Program referenced above subject to these Program Terms & Conditions (“Program Terms”). Each entity participating in the Program is hereinafter referred to as a “Participant.” Participation in the Program is voluntary. The Program is governed by the Program Terms, which incorporate by reference the Microsoft Partner Network Agreement (as in effect between Microsoft and Participant, the “MPN Agreement”). Capitalized terms used but not defined in these Program Terms have the meanings assigned to them in the MPN Agreement. These Program Terms are subject to local requirements and may vary by jurisdiction, and Participant retains sole discretion to set pricing for sales of applicable products.
Proposed Goods and Services Proposed Goods and Services pdf D/M/WBE Certification OPTIONAL No response Warranty No response
Overview (a) The Employer is committed to maintaining a stable and skilled workforce, recognising its contribution to the operation of the Employer. As such, full time direct and ongoing employment is a guiding principle of this Agreement. (b) The Employer will take all measures to achieve employment security for the direct permanent employees of the Employer. The Parties agree upon the measures in this Clause to protect and enhance the employment security, health and safety, terms and conditions of employment and career development of the employees. (c) The employer agrees that it is highly important to ensure that work is performed effectively, efficiently and without undue pressure or bullying, and in a way that promotes OHS and EO principles and practices in the workplace and appropriate representation of employees should they so request. The employer will ensure that its employment practices are consistent with the above principles and practices.
Project Overview Project Title [Drafting note: ARENA to complete. Insert full long name in accordance with ARENA’s naming convention] i.e. [GMS Number] [Powerworks, voltage control on the Pacific Islands Study] [GMS Number] [study/ project/ fellowship/ scholarship/ R&D Project] Contract Number [Drafting note: ARENA to complete – to be obtained from ARENA’s GMS] Recipient [Drafting note: Recipient to insert full legal name and ABN] Guidelines and policies Advancing Renewables Program – Program Guidelines, 2020 (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/XXXXX_XXX_Xxxxxxxxxx_XX_Xxxxxx_Xxxxx_XXXXX.xxx) ARENA Variation Policy (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxxx-xxxxxxxxx-xxxxxxxxx-xxxxxx.xxx) ARENA Report Writing Guidelines (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxx-xxxxxxx-xxxxxxxxxx.xxx)
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.
Drawings and Specifications 9.1 A complete list of all Drawings that form a part of the Contract Documents are to be found as an index on the Drawings themselves, and/or may be provided to Developer and/or in the Table of Contents. 9.2 Materials or Work described in words that so applied have a well-known technical or trade meaning shall be deemed to refer to recognized standards, unless noted otherwise. 9.3 Trade Name or Trade Term It is not the intention of the Contract Documents to go into detailed descriptions of any materials and/or methods commonly known to the trade under “trade name” or “trade term.” The mere mention or notation of “trade name” or “trade term” shall be considered a sufficient notice to Developer that it will be required to complete the work so named, complete, finished, and operable, with all its appurtenances, according to the best practices of the trade. 9.4 The naming of any material and/or equipment shall mean furnishing and installing of same, including all incidental and accessory items thereto and/or labor therefor, as per best practices of the trade(s) involved, unless specifically noted otherwise. 9.5 Contract Documents are complementary, and what is called for by one shall be binding as if called for by all. As such, Drawings and Specifications are intended to be fully cooperative and to agree. However, if Developer observes that Drawings and Specifications are in conflict with the Contract Documents, Developer shall promptly notify District and Architect in writing, and any necessary changes shall be made as provided in the Contract Documents. 9.6 Figured dimensions shall be followed in preference to scaled dimensions, and Developer shall make all additional measurements necessary for the work and shall be responsible for their accuracy. Before ordering any material or doing any work, each Developer shall verify all measurements at the building and shall be responsible for the correctness of same. 9.7 Should any question arise concerning the intent or meaning of the Contract Documents, including the Plans and Specifications, the question shall be submitted to the District for interpretation. If a conflict exists in the Contract Documents, these Construction Provisions shall control over the Facilities Lease, which shall control over the Site Lease, which shall control over Division 1 Documents, which shall control over Division 2 through Division 49 documents, which shall control over figured dimensions, which shall control over large-scale drawings, which shall control over small-scale drawings. In no case shall a document calling for lower quality and/or quantity of material or workmanship control. However, in the case of discrepancy or ambiguity solely between and among the Drawings and Specifications, the discrepancy or ambiguity shall be resolved in favor of the interpretation that will provide District with the functionally complete and operable Project described in the Drawings and Specifications. 9.8 Drawings and Specifications are intended to comply with all laws, ordinances, rules, and regulations of constituted authorities having jurisdiction, and where referred to in the Contract Documents, the laws, ordinances, rules, and regulations shall be considered as a part of the Contract Documents within the limits specified. 9.9 As required by Section 4-317(c), Part 1, Title 24, CCR: “Should any existing conditions such as deterioration or non-complying construction be discovered which is not covered by the DSA-approved documents wherein the finished work will not comply with Title 24, California Code of Regulations, a construction change document, or a separate set of plans and specifications, detailing and specifying the required repair work shall be submitted to and approved by DSA before proceeding with the repair work.”
Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.
