Job Request Registry Sample Clauses

Job Request Registry. The Corporation will maintain a ‘Job Request Registry’ whereby employees may inform the Corporation of their interest in specific jobs within the bargaining unit for future job transfer, promotion or demotion. The Registry will enable the Corporation to implement an expedited internal job placement process.
AutoNDA by SimpleDocs

Related to Job Request Registry

  • New Survey Requested Buyer will, at the ☐ Seller’s ☐ Buyer’s ☐ Shared expense and within a timeframe allowed to deliver and examine title evidence, obtain a certified survey of the Property from a certified and registered surveyor within the State. If the survey reveals encroachments on the Property or that the improvements encroach on the lands of another, such encroachments will constitute a title defect. The Buyer shall have the right to terminate this Agreement with written notice to the Seller within calendar days of being notified of said title defect.

  • Account Registration (a) Custodian shall open and maintain one or more custody accounts in the name of Customer and shall act pursuant to the terms of this Agreement. Each such account opened and maintained by Custodian shall be referred to herein as a “

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

  • Procedures for LNP Request The Parties shall provide for the requesting of End Office LNP capability on a reciprocal basis through a written request. The Parties acknowledge that Verizon has deployed LNP throughout its network in compliance with FCC 96-286 and other applicable FCC Regulations.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.

  • Inspection; Acceptance The Contractor (immixTechnology, Inc.) can only, and shall only tender for acceptance those items that substantially conform to the software manufacturer’s (“Dassault Systemes Americas Corp.”) published specifications. Therefore, items delivered shall be considered accepted upon delivery. The Government reserves the right to inspect or test any supplies or services that have been delivered. The Government may require repair or replacement of nonconforming supplies or re-performance of nonconforming services at no increase in contract price. If repair/replacement or re-performance will not correct the defects or is not possible, the Government may seek an equitable price reduction or adequate consideration for acceptance of nonconforming supplies or services. The Government must exercise its post-acceptance rights-

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

  • INSTRUCTIONAL MINUTES When CONTRACTOR is a NPS, the total number of instructional minutes per school day provided by CONTRACTOR shall be at least equivalent to the number of instructional minutes per school day provided to students at like grade level attending LEA schools and shall be specified in the student’s ISA developed in accordance with the student’s IEP. For students in grades kindergarten through 12 inclusive, unless otherwise specified in the student’s IEP and ISA, the number of instructional minutes, excluding breakfast, recess, lunch and passing time shall be at the same level that Ed. Code prescribes for the LEA. The total number of annual instructional minutes shall be at least equivalent to the total number of annual instructional minutes provided to students attending LEA schools in like grade level unless otherwise specified in the student’s IEP. When CONTRACTOR is a NPA and/or related services provider, the total number of minutes per school day provided by CONTRACTOR shall be specified in the student’s ISA developed in accordance with the student’s IEP.

  • Per-­‐Registrar Transactions Report This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐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 per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA 02 iana-­‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-­‐ids 03 total-­‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-­‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-­‐adds-­‐1-­‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.

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