Legal dispute regarding wages etc. Disputes about payment for work are dealt with according to the provisions on legal disputes regarding wages in § 10.
Legal dispute regarding wages etc Sample Clauses
Related to Legal dispute regarding wages etc
Alternative Dispute Resolution Limitations This is a requirement of the TIPS Contract and is non-negotiable. No Waiver of TIPS Immunity This is a requirement of the TIPS Contract and is non-negotiable. 5 5 Payment Terms and Funding Out Clause This is a requirement of the TIPS Contract and is non-negotiable. 6
Referral to Arbitration: Provincial Matters a. If the grievance is not resolved at Step Three within ten (10) working days of the meeting referred to in Article A.6.4, the BCTF or BCPSEA where applicable may refer a “provincial matters grievance,” as defined in Appendix 1 and Addenda, to arbitration within a further fifteen (15) working days. b. The referral to arbitration shall be in writing and should note that it is a “provincial matters grievance.” The parties shall agree upon an arbitrator within ten (10) working days of such notice.
Referral to Arbitration: Local Matters a. If the grievance is not resolved at Step Three within ten (10) working days of the meeting referred to in Article A.6.4, the local or the employer where applicable may refer a "local matters grievance," as defined in Appendix 2 and Addenda, to arbitration within a further fifteen (15) working days. b. The referral to arbitration shall be in writing and should note that it is a “local matters grievance.” The parties shall agree upon an arbitrator within ten (10) working days of such notice.
Dispute Resolution Mechanisms Registry Operator will comply with the following dispute resolution mechanisms as they may be revised from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PDDRP or RRDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. CONTINUED OPERATIONS INSTRUMENT The Continued Operations Instrument shall (a) provide for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6th) anniversary of the Effective Date, and (b) be in the form of either (i) an irrevocable standby letter of credit, or (ii) an irrevocable cash escrow deposit, each meeting the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof (which is hereby incorporated by reference into this Specification 8). Registry Operator shall use its best efforts to take all actions necessary or advisable to maintain in effect the Continued Operations Instrument for a period of six (6) years from the Effective Date, and to maintain ICANN as a third party beneficiary thereof. If Registry Operator elects to obtain an irrevocable standby letter of credit but the term required above is unobtainable, Registry Operator may obtain a letter of credit with a one-year term and an “evergreen provision,” providing for annual extensions, without amendment, for an indefinite number of additional periods until the issuing bank informs ICANN of its final expiration or until ICANN releases the letter of credit as evidenced in writing, if the letter of credit otherwise meets the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof; provided, however, that if the issuing bank informs ICANN of the expiration of such letter of credit prior to the sixth (6th) anniversary of the Effective Date, such letter of credit must provide that ICANN is entitled to draw the funds secured by the letter of credit prior to such expiration. The letter of credit must require the issuing bank to give ICANN at least thirty (30) calendar days’ notice of any such expiration or non-renewal. If the letter of credit expires or is terminated at any time prior to the sixth (6th) anniversary of the Effective Date, Registry Operator will be required to obtain a replacement Continued Operations Instrument. ICANN may draw the funds under the original letter of credit, if the replacement Continued Operations Instrument is not in place prior to the expiration of the original letter of credit. Registry Operator shall provide to ICANN copies of all final documents relating to the Continued Operations Instrument and shall keep ICANN reasonably informed of material developments relating to the Continued Operations Instrument. Registry Operator shall not agree to, or permit, any amendment of, or waiver under, the Continued Operations Instrument or other documentation relating thereto without the prior written consent of ICANN (such consent not to be unreasonably withheld). If, notwithstanding the use of best efforts by Registry Operator to satisfy its obligations under the preceding paragraph, the Continued Operations Instrument expires or is terminated by another party thereto, in whole or in part, for any reason, prior to the sixth anniversary of the Effective Date, Registry Operator shall promptly (i) notify ICANN of such expiration or termination and the reasons therefor and (ii) arrange for an alternative instrument that provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date (an “Alternative Instrument”). Any such Alternative Instrument shall be on terms no less favorable to ICANN than the Continued Operations Instrument and shall otherwise be in form and substance reasonably acceptable to ICANN. Notwithstanding anything to the contrary contained in this Specification 8, at any time, Registry Operator may replace the Continued Operations Instrument with an Alternative Instrument that (i) provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date, and (ii) contains terms no less favorable to ICANN than the Continued Operations Instrument and is otherwise in form and substance reasonably acceptable to ICANN. In the event Registry Operator replaces the Continued Operations Instrument either pursuant to paragraph 2 or this paragraph 3, the terms of this Specification 8 shall no longer apply with respect to the original Continuing Operations Instrument, but shall thereafter apply with respect to such Alternative Instrument(s), and such instrument shall thereafter be considered the Continued Operations Instrument for purposes of this Agreement. REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may (a) reserve names from registration pursuant to Section 2.6 of the Agreement and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification; provided, however, ICANN shall not disclose Confidential Information contained in such results except in accordance with Section 7.15 of the Agreement. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.
GRIEVANCE AND ARBITRATION PROCEDURES A. A grievance is a dispute, claim, or complaint arising under this Agreement, filed by either an authorized representative of or an employee in the Bargaining Unit, or the County, involving the interpretation or application of this Agreement. All discipline shall be for just cause. B. Grievances will be processed in the following manner and strictly in accordance with the following stated time limits: Step 1. The aggrieved employee shall be accorded fifteen (15) working days from the occurrence of the action or event or when the employee has knowledge or should have had knowledge of the action or the event giving rise to the complaint to seek resolution on an informal basis. The Employee must discuss his alleged grievance with the Airport Fire Chief and the Fire Rescue Division Director. If informal resolution is not accomplished, the employee, if a Union member, must present the proposed grievance in writing to a Union officer on or before the fifteenth (15th) working day for consideration by the Union Grievance committee. If, in the Committee's opinion, no reasonable grievance exists, no further action may be taken. Step 2. If the Committee wishes to pursue the member's complaint, a written grievance shall be presented to the Director of the Fire Rescue Division or his designee within twenty (20) working days from the occurrence of the action or event giving rise to the grievance or from the date on which the employee reasonably should have had knowledge of that occurrence. A written grievance must be presented on a grievance form provided by the County in Appendix A. Upon receipt of a formal grievance or a class action submitted by the Union, the Fire Rescue Division Director or his designee shall investigate the facts and conduct a meeting within five (5) working days with the aggrieved employee and any other persons possessing knowledge considered critical by the Director. The aggrieved employee may be accompanied at this meeting by a local Union representative. The Fire Rescue Division Director or his designee shall notify the grievant of his decision no later than five (5) working days following the date of the meeting. Step 3. If the grievance is not resolved at the second step, the aggrieved employee shall present the written grievance within five (5) working days of the Step 2 decision to the Department Head. The Department Head or his designee shall investigate the facts and may conduct a hearing within five
Customer Service, Dispute Resolution If you have a question about your XOOM charges or service you may contact XOOM directly by calling 0-000-000-0000 Monday – Friday 8 (eight) a.m. to 11 (eleven)p.m.
GRIEVANCE AND ARBITRATION 15.01 Either the Employer, the Union or any employee has a right to lodge a grievance with respect to any matter arising out of this Agreement or concerning the interpretation, application or alleged violation of this Agreement. 15.02 Any employee believing that he has been unjustly dealt with or that the provisions of this Agreement have not been complied with, shall have the right to place such grievances in the hands of the Union for review and adjustment by the Employer, if necessary. Such grievances shall be processed as follows: - Between the employee concerned, his Union representative and the Company. The grievance must be filed within eighteen (18) working days after the event giving rise to the grievance occurs and within this period of time it shall be discussed at this Step. The Manager shall give an oral decision within four (4) working days from the date the discussion took place. If the Union wishes to appeal to the next Step, the grievance shall be reduced to writing and the appeal shall be filed with the Store Manger within six (6) working days from the Store Manager's oral decision. Between the employee concerned, the Union representative, the Department Manager, and the Company. The discussion at this Step shall be held within seven (7) working days of the date of the appeal. The decision of the Employer at this Step shall be in writing and be made within four (4) working days of the date of the meeting. Should the Union wish to appeal, such notice of appeal must be in writing to the Company/operator within one (1) week of the decision of the Company at STEP TWO. The grievance shall be forwarded to the Employer, which shall have one (1) week to dispose of the grievance. The disposition shall be in writing and returned to the officers of the Union. If considered necessary by the parties, a meeting may be held by the parties and may include the interested persons. If a meeting is held, the decision shall be given to the other party within seven (7) days from the date of the meeting. 15.03 In the case of a dismissal, a grievance may be filed by an employee who feels he was unjustly dealt with. Such grievance must be filed within five (5) working days from the date of dismissal and shall commence at STEP TWO. In any subsequent disposal of this case during the grievance procedure, the Employer may re-instate the employee with full back pay, suspend the employee for a definite period or sustain the discharge. 15.04 Grievances concerning rates shall be handled in accordance with the above procedure and the disposition of such grievances, if sustained, shall include the determination of the effective date of the increase with retro-activity thereto. 15.05 The Employer and the Union may file grievances commencing at STEP THREE. (a) Failing settlement under the foregoing procedure, such grievance may be submitted to Arbitration, as hereinafter provided; (b) The time limits as prescribed above may be modified by mutual agreement of the parties.
GRIEVANCE AND ARBITRATION PROCEDURE 8.01 The parties to this agreement believe it is important to adjust complaints and grievances as quickly as possible as provided for herein. The employee or Union shall first discuss any individual complaint informally with the Director of Care or designate at the first opportunity. 8.02 In all steps of this grievance procedure an aggrieved employee, if she so desires may be accompanied by or represented by her Union Representative. At Step 1 of the grievance procedure a representative of the Ontario Nurses' Association may be present at the request of either party. 8.03 Should any dispute arise between the Employer and an employee, or between the Employer and the Union, as to the interpretation, application, administration or alleged violation of any of the provisions of this Agreement, the employee or Union Representative will bring it to the attention of the immediate supervisor to settle such differences within ten (10) days of the occurrence. If further action is to be taken, then within ten (10) days of the discussion, the employee, who may request the assistance of her Union Representative and/or Labour Relations Officer, shall submit the written grievance to the Administrator or designate. A meeting will be held between the parties within ten (10) days. The Administrator shall give a written decision within ten (10) days of the meeting to the Bargaining Unit President or her designate with a copy to the Labour Relations Officer. Should the Administrator fail to render his decision or failing settlement of any grievance under the foregoing procedure, including any questions as to whether a matter is arbitrable, the grievance may be referred to arbitration by either party. If no written notice of intent to submit the matter for arbitration is received within ten (10) days after the decision under Step No. 1 is received, the grievance shall be deemed to have been settled or abandoned. 8.04 A written grievance will indicate the nature of the grievance and the remedy sought by the grievor. Union grievances shall be set out on the union grievance form. Alternately, the parties may agree to an electronic version of this form and a process for signing. 8.05 Time limits fixed in the grievance and arbitration procedures may be extended only by written, mutual consent of the parties. Should the Employer not respond within the time limit(s) fixed, such failure to respond shall be deemed to be a denial of the grievance. Should a grievance not be submitted within the various time limits specified in this Agreement, unless mutually extended, it shall be considered to have been settled or abandoned.
Dispute Resolution Mechanism a. Any dispute regarding the administration of the Institute at the Company or plant level shall be subject to expedited resolution by the Chairs of the Union and Company Negotiating Committees and the Executive Director of ICD who shall apply the policies, rules and regulations of the Governing Board and the provisions of this Section in ruling on any such dispute. Rulings of the Executive Director may be appealed to the Governing Board, but shall become and remain effective unless stayed or reversed by the Governing Board. b. Within sixty (60) days of the Effective Date, the parties will develop an expedited dispute resolution mechanism that resolves disputes within two (2) weeks.
Labor Disputes No labor disturbance by or dispute with employees of the Company or any of its Subsidiaries exists or, to the knowledge of the Company, is threatened which would reasonably be expected to result in a Material Adverse Effect.
