Operational Roster Clause Samples

The Operational Roster clause defines the list of personnel or roles assigned to perform specific duties or functions within an organization or project. It typically outlines who is responsible for particular operational tasks, how the roster is maintained or updated, and may specify procedures for substituting or replacing rostered individuals. This clause ensures that all parties are clear about who is accountable for operational responsibilities, thereby promoting efficiency and minimizing confusion during the execution of activities.
POPULAR SAMPLE Copied 1 times
Operational Roster. (a) The Operational Roster is the actual roster that the Employer is requiring the employees to work and will show all shifts to be worked for the period of the roster. (b) The Operational Roster will display shift times and the location where the shift break is anticipated to be taken. The details of the relief line working will also be incorporated unless otherwise agreed between the Parties to this Agreement. (c) The lines of work for employees on successive Operational Rosters will follow each line of work on the Guide Roster in sequence by: (i) as far as reasonably practicable following the Rostered Day Off pattern in the Guide Roster except for periods of rostered leave, training, alternate duties or performance management; and (ii) taking the timing of shifts in the Guide roster into account as a relevant factor in the compilation of the Operational Rosters. (d) Following an authorized absence from work, the Operational Roster for an employee will resume following the line on the roster that they would have reached if no absence from work had occurred. If the absence exceeds six months, this may not be guaranteed. (e) Subject to subclause 3.1.7 and to any alternative agreed between the Parties to this Agreement, the Operational Roster may include rostered overtime with employees able to be rostered for up to eighty-five (85) hours per fortnightly cycle, provided that: (i) the average Standard Hours worked by all rostered employees in any fortnightly cycle under any posted Operational Roster shall not exceed 80; and (ii) any objection by an employee to being rostered to work overtime shall be raised with the employee's supervisor by the end of their second shift after the roster is posted and shall be dealt with as if it were an objection to working additional hours. (f) Unless otherwise agreed between the Parties to this Agreement, each fortnightly cycle of the Operational Roster should be posted 3 weeks in advance by Thursday at 1300 hours unless there are mitigating operational circumstances, in which case the roster will be posted by 1300 on Friday. (g) Where an employee requests a change to their Operational Roster within five calendar days after the Operational Roster has been posted, the Employer will consider that request. The decision whether to agree to the request shall be within the managerial prerogative of the Employer, provided that the shift as rostered is not unreasonable. Where a request is not agreed to, the employee will be requir...
Operational Roster. The Employer shall post a draft of the Operational Roster at least two weeks prior to the day of its implementation.
Operational Roster. The Employer shall post the Operational Roster at least two weeks prior to the day of its implementation. The Employer shall post a revised Operational Roster to incorporate approved “shift changes” and any other known operational contingencies at least five days prior the day of its implementation. The Operational Roster: is the actual roster that the Employer is requiring the Employees to work and will show all shifts to be worked for the period of the roster; shall be based on Employees working through each line of work on the Base Roster in sequence; shall take into account leave and other authorised absences and any other temporary customer, operational or organisational requirements including public holidays, special events and training; shall display shift start and finish times and locations; shall not roster an Employee to work an ordinary hours shift on a day shown on the Base Roster as a Protected Day Off or other rostered day off unless: the Employee has agreed to work that day; the Employee is shown as working a Relief Line on the Base Roster and required to relieve another rostered Employee; or the Employee has been given at least four weeks’ written notice of the Employer’s intention to roster an ordinary shift on that day and the shift is required for Employee training, or during Perth Royal Show or for another reason agreed between the Parties.
Operational Roster a) The Operational Roster is a 48-hour roster that identifies an Employee’s anticipated start and finish times per shift. b) The Operational Roster is determined by train scheduling. c) The Operational Roster is forecast for a 48-hour period and may be changed subject to Lift Up and Lay Back provisions contained within the Agreement. d) Employees will be provided an electronic copy the Operational Roster no less than 48 hours prior to commencement of each shift. In the event an electronic copy is not available, employees will be notified via telephone of their operational roster. e) Employees required to work beyond midnight on the final shift of their four-shift rostered on period, will be paid 170% for any time worked from midnight until 6am. f) Employees returning to work after a ROP, will not be rostered earlier than 6am unless subject to Lift up/Lay Back requirements or by mutual agreement to change the start time. Any work undertaken prior to 6am until 6am will be paid at 170%.
Operational Roster 

Related to Operational Roster

  • Synchronization, Commissioning and Commercial Operation 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including 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 SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG 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. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • Quality Service Standards Price Services and the Fund may from time to time agree to certain quality service standards, as well as incentives and penalties with respect to Price Services’ Services hereunder.

  • System Operations Each party, at its own expense, shall provide and maintain the equipment, software, services and testing necessary to transmit Data Communications to, and receive Data Communications from the parties’ respective Receipt Computers.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic County PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than twenty-four (24) hours.

  • System Operation The Parties shall adhere to any applicable operational requirements of PJM necessary to protect the integrity of the transmission system within the PJM Control Area and the transmission systems of interconnected control areas, and shall satisfy any and all PJM, RFC and NERC criteria, when applicable. The DS Supplier shall also adhere to any applicable operational requirements of the Company necessary to protect the integrity of the Company’s local distribution system.