Casual Labour 19.1.1 A casual employee is an employee employed on an occasional basis and whose work pattern is not regular and systematic. When a person is engaged for casual employment the employee will be informed in writing that the employee is to be employed as a casual, the job to be performed, the classification level, the actual or likely length of engagement including number of hours to be worked per week, and the relevant rate of pay. 19.1.2 A casual employee shall be entitled to all the applicable rates and conditions of employment prescribed in this Agreement except annual leave, personal leave, parental leave, jury service and public holidays. 19.1.3 On each occasion a casual employee is required to attend work the employee shall be entitled to payment for a minimum of four hours work plus the relevant fares and travel allowance. 19.1.4 A casual employee for working ordinary hours shall be paid 125 percent of the hourly rate prescribed in this Agreement for the employees’ classification. 19.1.5 A casual employee required to work overtime or weekend shall be entitled to the relevant penalty rates prescribed in this Agreement provided that: Where the relevant penalty rate is time and a half the employee shall be paid 175 percent of the hourly rate prescribed in this Agreement for the employee’s classification and where the relevant penalty rate is double time the employee shall be paid 225 percent of the hourly rate prescribed in this Agreement for the employee's classification. 19.1.6 A casual employee required to work on a public holiday shall be paid 275 percent of the hourly rate prescribed in this Agreement for the employee's classification. 19.1.7 Termination of all casual employment shall require one hours notice on either side or the payment or forfeiture of one hours pay, as the case may be.
Under-Frequency and Over Frequency Conditions The New York State Transmission System is designed to automatically activate a load- shed program as required by the NPCC in the event of an under-frequency system disturbance. Developer shall implement under-frequency and over-frequency relay set points for the Large Generating Facility as required by the NPCC to ensure “ride through” capability of the New York State Transmission System. Large Generating Facility response to frequency deviations of predetermined magnitudes, both under-frequency and over-frequency deviations, shall be studied and coordinated with the NYISO and Connecting Transmission Owner in accordance with Good Utility Practice. The term “ride through” as used herein shall mean the ability of a Generating Facility to stay connected to and synchronized with the New York State Transmission System during system disturbances within a range of under-frequency and over-frequency conditions, in accordance with Good Utility Practice and with NPCC Regional Reliability Reference Directory # 12, or its successor.
Cost Responsibility for Interconnection Facilities and Distribution Upgrades 4.1 Interconnection Facilities 4.2 Distribution Upgrades
Completion of Concrete Pours and Emergency Work (a) Except as provided in this sub-clause an Employee shall nor work or be required to work in the rain. (b) Employees shall not be required to start a concrete pour in Inclement Weather. (c) Where a concrete pour has been commenced prior to the commencement of a period of Inclement Weather Employees may be required to complete such concrete pour to a practical stage and for such work shall be paid at the rate of double time calculated to the next hour, and in the case of wet weather shall be provided with adequate wet weather gear. (d) If an Employee’s clothes become wet as a result of working in the rain during a concrete pour the Employee shall, unless the Employee has a change of dry working clothes available, be allowed to go home without loss of pay. (e) The provisions of clauses 32.7(c) and 32.7(d) hereof shall also apply in the case of emergency work where the Employees concerned and their delegates agree that the work is of an emergency nature and can start and/or proceed.
Early Construction of Base Case Facilities Developer may request Connecting Transmission Owner to construct, and Connecting Transmission Owner shall construct, subject to a binding cost allocation agreement reached in accordance with Attachment S to the ISO OATT, including Section 25.8.7 thereof, using Reasonable Efforts to accommodate Developer’s In-Service Date, all or any portion of any System Upgrade Facilities or System Deliverability Upgrades required for Developer to be interconnected to the New York State Transmission System which are included in the Base Case of the Class Year Study for the Developer, and which also are required to be constructed for another Developer, but where such construction is not scheduled to be completed in time to achieve Developer’s In-Service Date.
Use Cases Subscription Services are provided for Software only when used for its supported purpose (“Use Case”). The Use Case determines which Subscription is required and what fees are charged. If you use or deploy the Software in a manner contrary to a supported Use Case, you are responsible for purchasing the appropriate Subscription(s) to cover such usage. For example, if you are using a Red Hat Enterprise Linux Desktop Subscription as a server, you are obligated to purchase a Red Hat Enterprise Linux Server Subscription.
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.
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.
Participating TO’s Interconnection Facilities The Participating TO shall design, procure, construct, install, own and/or control the Participating TO’s Interconnection Facilities described in Appendix A at the sole expense of the Interconnection Customer. Unless the Participating TO elects to fund the capital for the Participating TO’s Interconnection Facilities, they shall be solely funded by the Interconnection Customer.
Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor
