Schedule Trades Sample Clauses

Schedule Trades. Trades in schedules mutually agreed to by nurses will be 18 subject to prior authorization by the Employer. The bases upon which the 19 Employer, in its discretion, may withhold authorization are (1) lack of 20 qualifications or orientation of the substituting nurse, or (2) the trade would 21 result in a premium pay obligation which would not otherwise have existed, and 22 such premium pay is not waived by the nurse. Waiver of overtime which would 23 violate state or federal law will not be an acceptable waiver under the 24 preceding sentence. 25
Sample 1See All (6)
AutoNDA by SimpleDocs
Schedule Trades. Trades in schedules mutually agreed to by nurses will be subject to prior authorization by the Employer. The bases upon which the Employer, in its discretion, may withhold authorization are (1) lack of qualifications or orientation of the substituting nurse, or (2) the trade would result in a premium pay obligation which would not otherwise have existed, and such premium pay is not waived by the nurse. Waiver of overtime which would violate state or federal law will not be an acceptable waiver under the preceding sentence.
Sample 1Sample 2
Schedule Trades. There are no restrictions on the number schedule 10 trades between qualified nurses. Although no schedule trade is allowed to result in the 11 payment of premium or overtime pay at the time of the request, such pay shall not be 12 excluded as a result of subsequent work being scheduled by the Medical Center and 13 performed by the nurse following the approval of the trade. The Medical Center may 14 deny a schedule trade request only if the nurse making the request is not qualified, or 15 the exchange will result in overtime or premium pay that would otherwise have not been 16 incurred. Once a trade has been approved the nurse relinquishing the shift has no 17 further responsibility for working the traded shift.
Sample 1

Related to Schedule Trades

  • State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.

  • Contents of Personnel File A. Adverse statements prepared by the County shall not be included in an employee's official personnel file unless a copy is provided to the employee. B. An employee shall have the right to inspect and review the contents of his or her official personnel file at reasonable intervals. C. In addition, an employee shall have the right to inspect and review the contents of his or her official personnel file in any case where the employee has a grievance related to performance; to a performance evaluation; or is contesting his or her suspension or discharge from County service. D. Letters of reference and reports concerning criminal investigations concerning the employee shall be excluded from the provisions of B. and C., above. E. An employee shall have the right to respond in writing or personal interview to any information contained in his or her official personnel file, such reply to become a permanent part of such employee's official personnel file. F. Any contents of an employee's official personnel file may be destroyed pursuant to an agreement between the Chief of Employee Relations and the employee concerned or by an order of an arbitrator, court or impartial hearing officer unless the particular item is otherwise required by law to be kept.

  • Obtaining Stock Exchange Listings The Company will from time to time take all commercially reasonable actions which may be necessary so that the Warrant Shares, immediately upon their issuance upon the exercise of Warrants, will be listed on the principal securities exchanges and markets within the United States of America, if any, on which other shares of Common Stock are then listed.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Review of Personnel File Upon written authority from an employee, OC shall permit the President of the Union or their designate to review that employee's personnel file in the office in which the file is normally kept in order to facilitate the proper investigation of a grievance.

  • Directory Listings 15.1.1 CBT, as publisher of its White Pages, will include Primary Listings of CLEC’s resale directory customers in its White Pages, and shall cause its publisher to include primary listings of CLEC’s directory customers in its Publisher’s Yellow Pages Directories under the following terms and conditions: 15.1.1.1 CBT will publish the Primary Listing of CLEC Directory Customers located within the geographic scope of its White Pages directory and will recover costs for both resale and facility based Customers in accordance with the Act.

  • Proposed Goods and Services Proposed Goods and Services pdf D/M/WBE Certification OPTIONAL No response Warranty No response

  • Commercially Useful Function A prime consultant can credit expenditures to a DBE subconsultant toward DBE goals only if the DBE performs a Commercially Useful Function (CUF). A DBE performs a CUF when it is responsible for execution of the work of a contract and carries out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the DBE must also be responsible, with respect to materials and supplies on the contract, for negotiating price, determining quality and quantity, ordering the material, and installing (where applicable) and paying for the material itself that it uses on the project. To determine whether a DBE is performing a commercially useful function, the Department will evaluate the amount of work subcontracted, industry practices, whether the amount the firm is to be paid under the contract is commensurate with the work it is actually performing and the DBE credit claimed for its performance of the work, and other relevant factors. A DBE will not be considered to perform a commercially useful function if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of DBE participation. In determining whether a DBE is such an extra participant, the Department will examine similar transactions, particularly those in which DBEs do not participate. If a DBE does not perform or exercise responsibility for at least 30 percent of the total cost of its contract with its own work force, or if the DBE subcontracts a greater portion of the work of a contract than would be expected on the basis of normal industry practice for the type of work involved, the Department will presume that the DBE is not performing a commercially useful function. When a DBE is presumed not to be performing a commercially useful function as provided above, the DBE may present evidence to rebut this presumption. The Department will determine if the firm is performing a CUF given the type of work involved and normal industry practices. The Department will notify the consultant, in writing, if it determines that the consultant’s DBE subconsultant is not performing a CUF. The consultant will be notified within seven calendar days of the Department’s decision. Decisions on CUF may be appealed to the ADOT State Engineer. The appeal must be in writing and personally delivered or sent by certified mail, return receipt requested, to the State Engineer. The appeal must be received by the State Engineer no later than seven calendar days after the decision of XXXX. XXXX’s decision remains in place unless and until the State Engineer reverses or modifies BECO’s decision. ADOT State Engineer will promptly consider any appeals under this subsection and notify the consultant of ADOT’s State Engineer findings and decisions. Decisions on CUF matters are not administratively appealable to USDOT. The BECO may conduct project site visits on the contract to confirm that DBEs are performing a CUF. The consultant shall cooperate during the site visits and the BECO’s staff will make every effort not to disrupt work on the project.

  • BACKGROUND STATEMENT The Borrower has requested that the Lenders make available a revolving credit facility in the aggregate principal amount of $400,000,000. The Lenders are willing to make available to the Borrower the revolving credit facility provided for herein subject to and on the terms and conditions set forth in this Agreement.

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