Procedure for Assignment to Permanent Midnight Shift Sample Clauses

Procedure for Assignment to Permanent Midnight Shift a. Assignment to a midnight shift will be accomplished through volunteers based on sen- iority as defined in Article 12. All bargaining unit members will be eligible for voluntary placement onto the midnight shift. MPOs shall bid with other MPOs as a class. Sergeants will bid with other sergeants as a class. b. In the event the number of officers volunteering for assignment to the midnight shift is insufficient, involuntary assignments will be made based on inverse seniority beginning with the least senior PO1 in the district. c. The duration of the midnight shift assignment will be a minimum of six months. Once an officer on the midnight shift meets the minimum time requirement, that officer may transfer off of the shift either at the end of the initial six months or at the end of the fiscal year quarter (i.e., every three months). Requests for transfer off of the midnight shift must occur two weeks prior to the end of any fiscal year quarter and will be honored at the end of the fiscal year quarter that follows the fiscal year quarter in which the request was made. d. Assignments onto the midnight shift will only be made on a fiscal year quarterly basis (i.e. every three months) and simultaneously with any departure from the midnight shift. Officers who are assigned to the midnight shift will be given notice of the assignment at the beginning of the fiscal quarter proceeding the quarter of their assignment. However, notice for voluntary transfer onto or off the midnight shift may be waived upon mutual agreement of the officer and the unit commander. e. When an officer is permanently transferred off of the midnight shift the effective date of the transfer will be recorded in the officer’s unit operating file. An officer who has received a departure date from midnights will not be involuntarily transferred back to the midnight shift if there are officers in the district who have either no departure date or an earlier departure date. f. An officer being initially assigned to a district or transferred into the district from another assignment will not be eligible for voluntary or involuntary transfer onto the midnight shift until the next fiscal quarter has passed, except when a vacancy exist, a unit member volunteers for assignment, and there is no waiting list of eligible volunteers. The initial permanent assignment of a PO1 who has successfully completed FTO may be the midnight shift. g. Any reassignment on or off the midnight shift will occur the first f...
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs

Related to Procedure for Assignment to Permanent Midnight Shift

  • Procedure for assignment (a) Subject to the conditions set out in Clause 23.2 (Conditions of assignment or transfer) an assignment may be effected in accordance with paragraph (c) below when the Agent executes an otherwise duly completed Assignment Agreement delivered to it by the Existing Lender and the New Lender. The Agent shall, subject to paragraph (b) below, as soon as reasonably practicable after receipt by it of a duly completed Assignment Agreement appearing on its face to comply with the terms of this Agreement and delivered in accordance with the terms of this Agreement, execute that Assignment Agreement. (b) The Agent shall only be obliged to execute an Assignment Agreement delivered to it by the Existing Lender and the New Lender once it is satisfied it has complied with all necessary “know your customer” or other similar checks under all applicable laws and regulations in relation to the assignment to such New Lender. (c) Subject to Clause 23.9 (Pro rata interest settlement), on the Transfer Date: (i) the Existing Lender will assign absolutely to the New Lender the rights under the Finance Documents expressed to be the subject of the assignment in the Assignment Agreement; (ii) the Existing Lender will be released by each Obligor and the other Finance Parties from the obligations owed by it (the “Relevant Obligations”) and expressed to be the subject of the release in the Assignment Agreement; and (iii) the New Lender shall become a Party as a “Lender” and will be bound by obligations equivalent to the Relevant Obligations. (d) Lenders may utilise procedures other than those set out in this Clause 23.6 to assign their rights under the Finance Documents (but not, without the consent of the relevant Obligor or unless in accordance with Clause 23.5 (Procedure for transfer), to obtain a release by that Obligor from the obligations owed to that Obligor by the Lenders nor the assumption of equivalent obligations by a New Lender) provided that they comply with the conditions set out in Clause 23.2 (Conditions of assignment or transfer).

  • ASSIGNMENT AND TRANSFER SIGNATURE LINES FOR VALUE RECEIVED, the undersigned Holder hereby sell(s), assign(s) and transfer(s) unto ______________________________ whose taxpayer identification number is _______________________ and whose address including postal zip code is ____________________________, the within Receipt and all rights thereunder, hereby irrevocably constituting and appointing ________________________ attorney-in-fact to transfer said Receipt on the books of the Depositary with full power of substitution in the premises.

  • Notification of Assignment of Receivables At any time following the occurrence of an Event of Default or a Default, Agent shall have the right to send notice of the assignment of, and Agent's security interest in, the Receivables to any and all Customers or any third party holding or otherwise concerned with any of the Collateral. Thereafter, Agent shall have the sole right to collect the Receivables, take possession of the Collateral, or both. Agent's actual collection expenses, including, but not limited to, stationery and postage, telephone and telegraph, secretarial and clerical expenses and the salaries of any collection personnel used for collection, may be charged to Borrowers' Account and added to the Obligations.

  • Termination of Assignment Citizens and the Firm may each terminate a specific assignment or all assignments held by the Firm, at any time upon advanced written notice. Citizens may also reassign any matter at any time upon advanced written notice.

  • Change of Control; Assignment and Subcontracting Except as set forth in this Section 7.5, neither party may assign any of its rights and obligations under this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any subcontracting arrangement that relates to any Critical Function (as identified in Section 6 of Specification 10) for the TLD (a “Material Subcontracting Arrangement”) shall be deemed an assignment. (a) Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any assignment or Material Subcontracting Arrangement, and any agreement to assign or subcontract any portion of the operations of the TLD (whether or not a Material Subcontracting Arrangement) must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of control of Registry Operator. (b) Within thirty (30) calendar days of either such notification pursuant to Section 7.5(a), ICANN may request additional information from Registry Operator establishing (i) compliance with this Agreement and (ii) that the party acquiring such control or entering into such assignment or Material Subcontracting Arrangement (in any case, the “Contracting Party”) and the ultimate parent entity of the Contracting Party meets the ICANN-­‐adopted specification or policy on registry operator criteria then in effect (including with respect to financial resources and operational and technical capabilities), in which case Registry Operator must supply the requested information within fifteen (15) calendar days. (c) Registry Operator agrees that ICANN’s consent to any assignment, change of control or Material Subcontracting Arrangement will also be subject to background checks on any proposed Contracting Party (and such Contracting Party’s Affiliates). (d) If ICANN fails to expressly provide or withhold its consent to any assignment, direct or indirect change of control of Registry Operator or any Material Subcontracting Arrangement within thirty (30) calendar days of ICANN’s receipt of notice of such transaction (or, if ICANN has requested additional information from Registry Operator as set forth above, thirty (30) calendar days of the receipt of all requested written information regarding such transaction) from Registry Operator, ICANN shall be deemed to have consented to such transaction. (e) In connection with any such assignment, change of control or Material Subcontracting Arrangement, Registry Operator shall comply with the Registry Transition Process. (f) Notwithstanding the foregoing, (i) any consummated change of control shall not be voidable by ICANN; provided, however, that, if ICANN reasonably determines to withhold its consent to such transaction, ICANN may terminate this Agreement pursuant to Section 4.3(g), (ii) ICANN may assign this Agreement without the consent of Registry Operator upon approval of the ICANN Board of Directors in conjunction with a reorganization, reconstitution or re-­‐incorporation of ICANN upon such assignee’s express assumption of the terms and conditions of this Agreement, (iii) Registry Operator may assign this Agreement without the consent of ICANN directly to a wholly-­‐owned subsidiary of Registry Operator, or, if Registry Operator is a wholly-­‐owned subsidiary, to its direct parent or to another wholly-­‐owned subsidiary of its direct parent, upon such subsidiary’s or parent’s, as applicable, express assumption of the terms and conditions of this Agreement, and (iv) ICANN shall be deemed to have consented to any assignment, Material Subcontracting Arrangement or change of control transaction in which the Contracting Party is an existing operator of a generic top-­‐level domain pursuant to a registry agreement between such Contracting Party and ICANN (provided that such Contracting Party is then in compliance with the terms and conditions of such registry agreement in all material respects), unless ICANN provides to Registry Operator a written objection to such transaction within ten (10) calendar days of ICANN’s receipt of notice of such transaction pursuant to this Section 7.5. Notwithstanding Section 7.5(a), in the event an assignment is made pursuant to clauses (ii) or (iii) of this Section 7.5(f), the assigning party will provide the other party with prompt notice following any such assignment.

  • Notification of Assignment Any assignment that is not undertaken in accordance with the provisions set forth above shall be null and void ab initio. A Party making any assignment shall promptly notify the other Party of such assignment, regardless of whether consent is required. This Agreement shall be binding upon and inure to the benefit of the Parties hereto and their respective successors and permitted assigns.

  • Complete Disposal Upon Termination of Service Agreement Upon Termination of the Service Agreement Provider shall dispose or delete all Student Data obtained under the Service Agreement. Prior to disposition of the data, Provider shall notify LEA in writing of its option to transfer data to a separate account, pursuant to Article II, section 3, above. In no event shall Provider dispose of data pursuant to this provision unless and until Provider has received affirmative written confirmation from LEA that data will not be transferred to a separate account.

  • Certification of Funds; Budget and Fiscal Provisions; Termination in the Event of Non-Appropriation This Agreement is subject to the budget and fiscal provisions of the City’s Charter. Charges will accrue only after prior written authorization certified by the Controller, and the amount of City’s obligation hereunder shall not at any time exceed the amount certified for the purpose and period stated in such advance authorization. This Agreement will terminate without penalty, liability or expense of any kind to City at the end of any fiscal year if funds are not appropriated for the next succeeding fiscal year. If funds are appropriated for a portion of the fiscal year, this Agreement will terminate, without penalty, liability or expense of any kind at the end of the term for which funds are appropriated. City has no obligation to make appropriations for this Agreement in lieu of appropriations for new or other agreements. City budget decisions are subject to the discretion of the Mayor and the Board of Supervisors. Contractor’s assumption of risk of possible non-appropriation is part of the consideration for this Agreement. THIS SECTION CONTROLS AGAINST ANY AND ALL OTHER PROVISIONS OF THIS AGREEMENT.

  • Annual Notification of Rights If the LEA has a policy of disclosing Education Records and/or Student Data under FERPA (34 CFR § 99.31(a)(1)), LEA shall include a specification of criteria for determining who constitutes a school official and what constitutes a legitimate educational interest in its annual notification of rights.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!