SENIORlTY CONVERSION TABLE Sample Clauses

SENIORlTY CONVERSION TABLE. In the event that an employee changes his/her job status to or from that of a Permanent Full-Time employee the following table will be used to convert hours to days and vice versa for the purpose of crediting seniority and determining the adjusted date of hire: 1960 paid hours = 1 year when normal full-time hours hours a week 1637.5 paid hours = 1 year when normal full-time hours = 37.5 hours a week 1715 paid hours = 1 year when normal full-time hours 35 hours a week Additional hours will be converted to days on a pro-rata basis using the above formula.
AutoNDA by SimpleDocs

Related to SENIORlTY CONVERSION TABLE

  • Termination for Convenience TIPS may, by written notice to Vendor, terminate this Agreement for convenience, in whole or in part, at any time by giving thirty (30) days’ written notice to Vendor of such termination, and specifying the effective date thereof.

  • Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx.

  • Reporting Requirements The Company, during the period when the Prospectus is required to be delivered under the 1933 Act or the 1934 Act, will file all documents required to be filed with the Commission pursuant to the 1934 Act within the time periods required by the 1934 Act and the 1934 Act Regulations.

  • Definitions and Interpretation 1.1 In this Agreement:

  • Payment Terms DXC agrees to pay Supplier the undisputed amount of an invoice within ninety (90) days after the receipt of a valid, complete and properly documented invoice. Any prompt payment discount will be calculated from the date a conforming invoice is received by DXC. Payment will be in U.S. currency unless otherwise stated. Payment will not constitute acceptance of Products and/or Services or impair DXC’s right to inspect. Acceptance shall be when DXC deems the Products and/or Services to meet its specified criteria (“Acceptance”). DXC, at its option, and without prior notice to Supplier, shall have the right to set off or deduct from any Supplier’s invoice, any credits, refunds or claims of any kind due DXC.

  • Reporting Provision Within 30 days of signing this Agreement, the District will submit for OCR’s review and approval the location and content of its Notice, as well as protocols and timeframes for responding to reports of barriers.

  • Order of Precedence Any ambiguity, conflict or inconsistency between the documents comprising this contract shall be resolved according to the following order of precedence:

  • NOTE For Community-­‐Based TLDs Only] Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-­‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at [insert applicable URL] with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.]

  • Representations and Warranties Borrower represents and warrants as follows:

  • Undue Burden and Fundamental Alteration For any technology-related requirement in this Agreement for which the Recipient asserts an undue burden or fundamental alteration defense, such assertion may only be made by the Superintendent or by an individual designated by the Superintendent and who has budgetary authority after considering all resources available for use in the funding and operation of the service, program, or activity, and must be accompanied by a written statement of the reasons for reaching that conclusion, including the cost of meeting the requirement and the available funding and other resources. The written statement will be certified by the determining official. If such a determination is made, the certifying official will describe in the written statement how it will provide equally effective alternate access, i.e., other action that would not result in such an alteration or such burdens but would nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services provided by the Recipient as their nondisabled peers.

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