Late Board Regulations Sample Clauses

Late Board Regulations. 1. A late Operator must report in person to Dispatch or contact their Assistant Manager no later than two (2) hours past their assigned report time. If a “Report” Operator is available, the late Operator’s assignment may go to the report Operator ahead of the late Operator. The Dispatcher shall have sole discretion in making the decision. If no Report Operator is available and the “late” Operator is only a few minutes late, he/she may be given their original run, but will be marked “late-worked run”.
AutoNDA by SimpleDocs

Related to Late Board Regulations

  • FCC Regulations The unstayed, effective regulations promulgated by the FCC, as amended from time to time.

  • Federal Reserve Regulations (a) None of Holdings, the Borrower or any of the Subsidiaries is engaged principally, or as one of its important activities, in the business of extending credit for the purpose of buying or carrying Margin Stock.

  • Regulation 274 - Hiring Practices The parties agree that it is critical that the process to gain long-term occasional assignments and permanent positions be fair and transparent.

  • Board of Governors (hereinafter called the Board) is the body referred to by that name in the Carleton University Act.

  • Leave Regulations The leave regulations in Subchapter 510 of the Employee and Labor Relations Manual, insofar as such regulations establish wages, hours and working conditions of employees covered by this Agreement, shall remain in effect for the life of this Agreement.

  • Technical Regulations 1. The rights and obligations of the Parties in respect of technical regulations, standards and conformity assessment shall be governed by the WTO Agreement on Technical Barriers to Trade.

  • EXPORT REGULATIONS Licensee agrees and accepts that Software may be subject to import and export laws of any country, including those of the European Union and United States (specifically the Export Administration Regulations (EAR)). Licensee acknowledges that it is not a citizen, national, or resident of, and is not under control of the governments of Cuba, Iran, North Korea, Sudan or Syria and is not otherwise a restricted end-user as defined by applicable export control laws. Further, Licensee acknowledges that it will not download or otherwise export or re-export Software or any related technical data directly or indirectly to the above-mentioned countries or to citizens, nationals, or residents of those countries, or to any other restricted end user or for any restricted end-use.

  • Margin Regulations Neither the making of any Loan hereunder nor the use of the proceeds thereof will violate the provisions of Regulation T, U or X of the Board.

  • Regulations The disclosures in the Registration Statement, the Sale Preliminary Prospectus, and Prospectus concerning the effects of federal, foreign, state, and local regulation on the Company’s business as currently contemplated are correct in all material respects and do not omit to state a material fact necessary to make the statements therein, in the light of the circumstances in which they were made, not misleading.

  • COMPLIANCE WITH FEDERAL, STATE AND LOCAL REGULATIONS If required within the Authorized User Agreement, Contractor will provide verification of compliance with specific Federal, State and local regulations, laws and IT standards that the Authorized User is required to comply with. See Appendix F – Primary Security and Privacy Mandates. AUTHENTICATION TOKENS The Authorized User Agreement may require authentication tokens for all systems. For more details, please see NYS ITS Policy S14-006 Authentication Tokens Standard or successor. MODIFICATION TO CLOUD SERVICE DELIVERY TYPE AND DESCRIPTION WITHIN AN AUTHORIZED USER AGREEMENT As Cloud services can be flexible and dynamic, delivery mechanisms may be subject to change. This may result in changes to the service type, description, or SKU. The State and Authorized Users require notification of any such changes to ensure security and business needs are met. Any changes to the description, type of service(s), or SKU (e.g., PaaS to IaaS) must be provided to OGS via Appendix C - Contract Modification Procedure. In addition, notification must be provided to the Authorized User for review and acceptance, prior to implementation. Any changes to the Authorized User Agreement will require the Authorized User to re-assess the risk mitigation methodologies and strategies and revise the Authorized User Agreement as needed.

Time is Money Join Law Insider Premium to draft better contracts faster.